| CVE |
Vendors |
Products |
Updated |
CVSS v3.1 |
| The CoE complete-access download handler iterated over all subindices of an object and wrote the master-supplied payload into each writable entry. Entries that hold a constant have write-access flags set but carry a NULL data pointer. The handler did not check for this and wrote the master payload through the NULL pointer. |
| An object dictionary entry that holds a constant has no process data storage and carries a NULL data pointer. sizeOfPDO did not check for this when resolving a mapped entry to its descriptor. A master that maps such an entry to a PDO causes COE_pdoPack or COE_pdoUnpack to dereference the NULL data pointer on every process data exchange after the mapping is activated. |
| ESC_eoeprocess and ESC_eoeprocess_tx can be reached before the application calls EOE_config to supply the callback table pointer. When eoe_cfg is NULL the receive handler dereferenced it while processing an incoming EoE frame, and the transmit polling function dereferenced it on each cycle, causing NULL pointer dereferences. |
| ESC_foeprocess can be reached by an incoming mailbox frame before the application calls FOE_config to supply the file table and flush buffer pointers. When foe_cfg or its fbuffer field is NULL the handler dereferenced those pointers while processing the frame, causing a NULL pointer dereference. |
| The EoE receive and transmit paths call the handle_recv_buffer and fetch_send_buffer callbacks without first checking whether they are set. Both callbacks are documented as optional; an application that omits either one causes a call through a NULL function pointer when the first EoE frame arrives or when the transmit polling loop runs. |
| The FoE file table allows entries to omit a write handler by setting write_function to NULL, making the file read-only. FOE_fopen did not check whether write_function was present before accepting a write request; a master sending a WRQ for a read-only file caused a call through a NULL function pointer. |
| The CoE SDO upload handler enters its normal-response path (used for objects longer than 4 bytes) and passes (objd + nsub)->data directly to the pre-object handler and to the response copy. Entries that hold a constant in the value field have data set to NULL; a master can request such an entry and cause a NULL pointer dereference in the upload path. |
| An object dictionary entry can carry write-access flags and still have a NULL data pointer, for example when a constant value is held in the value field rather than in addressable storage. The CoE SDO download handler checked write access but not whether storage was present, then wrote the master-supplied payload through the NULL pointer. |
| A CoE SDO request for index 0xFFFF matches the object list terminator entry instead of returning not-found. The terminator has a NULL objdesc pointer. Callers dereference it without checking, crashing the slave. |
| SDO_downloadsegment is called whenever a mailbox frame carries the DOWNLOADSEGREQ command byte, regardless of whether a segmented download is actually in progress. ESCvar.data, which the handler writes through, is NULL until a segmented transfer is started. A master can send a DOWNLOADSEGREQ at any time and write through a NULL or stale pointer. |
| In Eclipse Mosquitto versions 2.1.0 to 2.1.2, using the mosquitto_ctrl utility in interactive shell mode to interact with a malicious server could result in a crash of the utility if the server sent a hostile response. |
| In Eclipse Mosquitto versions 2.1.0 to 2.1.2, the mosquitto_ctrl utility would crash if attempting to interact with a hostile broker and the broker sent a non-string "error" value. |
| Issue summary: A DANE-enabled TLS client may crash by dereferencing a NULL
pointer when processing an unusual combination of certificate and TLSA
records.
Impact summary: The impact is limited to a client crash (potential Denial
of Service).
CWE: CWE-476: NULL Pointer Dereference
Description: A DANE-enabled TLS client that supports TLSA records with at
least one of the PKIX-TA(0) or PKIX-EE(1) usages alongside the DANE-TA(2)
usage may crash by dereferencing a NULL pointer if the server claims a trusted
CA's certificate to be its end-entity certificate and has an unusual mix of
associated TLSA records.
DANE SMTP clients should not be affected since only the
DANE-TA(2) and DANE-EE(3) TLSA record usages are specified applicable
in SMTP. For example, the Postfix MTA is not affected, while the Exim
MTA does not at present use OpenSSL's DANE implementation.
Use of DANE in validation of RFC7250 raw public keys (RPKs) is also
unaffected, as these only use DANE-EE(3) TLSA records.
Only applications that support combining the DANE PKI with a traditional PKI
are potentially affected. A DANE-enabled browser or similar, that uses
OpenSSL's DANE API could be affected.
FIPS impact: no
The DANE API is outside the FIPS module boundary. |
| In the Linux kernel, the following vulnerability has been resolved:
nvme-tcp: Validate the queue state under the queue lock in the address attribute
Reading the "address" sysfs attribute calls kernel_getsockname() on the
admin queue socket, which can race with the queue teardown during
connection error recovery: a reader can observe NVME_TCP_Q_LIVE set,
then block on the queue lock while nvme_tcp_free_queue() releases the
socket and clears queue->sock without holding the lock. Once the
reader acquires the lock it dereferences the NULL socket pointer.
Commit 76d54bf20cdc ("nvme-tcp: don't access released socket during
error recovery") had the queue liveness check inside the lock.
Commit 782373ba2766 ("nvme: tcp: avoid race between queue_lock lock
and destroy") moved it back out because the lock itself is destroyed
in nvme_tcp_free_queue(), so a reader arriving late trips
mutex_destroy().
Check the queue liveness inside the queue lock, and clear queue->sock
under the same lock. The teardown clears NVME_TCP_Q_LIVE under the
lock well before the socket is released, so a reader either sees the
bit cleared or a socket that cannot be released while it holds the
lock. To also close the lock lifetime race, the queue locks are now
owned by the controller: they are initialized with the queue array and
only destroyed when the controller is freed, which cannot happen while
a sysfs attribute read is still in progress. The queue count is
computed by the NVME_TCP_OPT_NR_QUEUES() macro from the original
connect options for both initialization and destruction, as reconnects
may shrink ctrl->queue_count. |
| In the Linux kernel, the following vulnerability has been resolved:
ksmbd: fix NULL pointer dereference in session_user_name() and session_account_type()
session_user_name() and session_account_type() dereference
session->user without checking for NULL. A session can be published
and exposed via the procfs session interface before authentication
completes, during which session->user is NULL:
show_proc_session() -> session_user_name(sess)
-> user_guest(session->user) -> NULL->flags -> oops
Guard both functions by treating a NULL session->user as an explicit
not-yet-authenticated state rather than dereferencing it. |
| MapServer is a system for developing web-based GIS applications. From 4.4.0 until 8.6.5, an unauthenticated remote attacker can send a WCS GetCoverage XML POST request whose BoundingBox element omits the crs attribute, causing xmlGetProp() in src/mapwcs.cpp to return null. msWCSParseRequest() then calls string functions on the null value before normal WCS exception handling, crashing the CGI or FastCGI worker. The analogous KVP or GET path is not affected because it obtains a count-validated, non-null token. A single request can terminate one worker, and repeated requests can exhaust a fixed worker pool and deny service. This issue is fixed in version 8.6.5. |
| Netatalk is a Free and Open Source file server suite for Unix-like operating systems. From 3.1.0 until 4.5.2, the Spotlight RPC consumer handlers sl_rpc_fetchAttributeNamesForOIDArray, sl_rpc_storeAttributesForOIDArray, and sl_rpc_fetchAttributesForOIDArray in etc/afpd/spotlight.c dereference the first element of a decoded sl_cnids_t without checking whether the inner CNID array is empty. An authenticated AFP client, or a guest when guest AFP access is enabled, can send a crafted SPOTLIGHT_CMD_RPC whose outer CNIDS length is greater than 16 while its inner count is zero, causing sl_unpack_cnids to create an empty DALLOC_CTX and the consumer to dereference dd_talloc_array[0]. The affected afpd child crashes, normally limiting denial of service to the attacker's session, and no memory write or code execution was demonstrated. This issue is fixed in version 4.5.2. |
| MP4v2 through 2.1.0 contains a NULL pointer dereference vulnerability in MP4RtpHintTrack::GetPayload() in src/rtphint.cpp that passes an unchecked rtpmap value to strchr(). Attackers can supply a crafted MP4 file whose RTP hint track has a corrupted hinf atom to crash mp4info or applications calling MP4GetHintTrackRtpPayload(). |
| ACN protocol dissector crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service |
| Exported PDU protocol dissector crash in 4.6.0 to 4.6.9 and 4.4.0 to 4.4.19 allows denial of service |