Padma81

The issue is related to an assertion failure in the `issuerAndThisUpdateCheck` function, which can occur via a crafted packet with a short timestamp, resulting in a denial of service (daemon exit). This is related to `schema init.c` and `checkTime`. The vulnerability can be exploited by a remote attacker, allowing them to send a specially crafted packet to `slapd` and execute a denial of service attack.

The issue is related to the function `g byte array new take()` in the GLib library, which is associated with the copying of a buffer without checking the size of the input data. If this function is called with a buffer of 4GB or more on a 64-bit platform, the length would be truncated modulo 2**32, causing unintended length truncation. This could potentially allow a remote attacker to execute arbitrary code.

The issue is related to an incompatible type access in the OpenLDAP protocol implementation. It allows a remote attacker to send a specially crafted request to slapd, potentially leading to a denial of service (DoS) attack. The flaw is in the ldap X509dn2bv function and affects the X.509 DN parsing in ad keystring, causing a slapd crash.

The issue is related to a double free vulnerability in the OpenLDAP protocol, which can be exploited by a remote attacker to cause a denial of service (DoS) by sending a specially crafted request to slapd. This can lead to a crash in the saslAuthzTo processing.

The issue is related to a double free memory error during the handling of the Values Return Filter control, which can lead to a denial of service (DoS) when a specially crafted request is sent to slapd. This can cause the slapd service to crash, resulting in an out-of-bounds read. The estimated number of potentially affected devices worldwide is not specified. There is no information about real-world incidents where this issue was exploited.

The issue arises from a NULL pointer dereference in the `pax decode header` function within `sparse.c` when parsing certain archives with malformed extended headers.

The issue is related to the mishandling of symlinks by systemd-tmpfiles in systemd, allowing local users to obtain ownership of arbitrary files. This occurs through the creation of a directory and a file under that directory, and later replacing that directory with a symlink. The issue persists even when the fs.protected symlinks sysctl is enabled.

The issue arises from curl's use of the outdated IDNA 2003 standard to handle International Domain Names, which may lead users to unknowingly issue network transfer requests to the wrong host. This is particularly problematic with domains using special characters, such as the German ß character, which is translated differently in IDNA 2003 and the modern IDNA 2008 standard. For instance, the domain `straße.de` is translated to `strasse.de` using IDNA 2003, but to `xn--strae-oqa.de` using IDNA 2008, potentially resolving to different addresses.

A flaw in the way curl handles cookies allows other threads to trigger a use-after-free, leading to information disclosure. This occurs because curl permits users to share cookies between multiple easy handles that are concurrently employed by different threads. When cookies are collected to be sent to a server, the matching function returns a list with references to the original strings, but if another thread quickly takes the lock and frees one of the original cookie structs together with its strings, a use-after-free can occur. Additionally, another thread can replace the contents of the cookies from separate HTTP responses or API calls.

The issue affects confidentiality, integrity, and availability. It is related to vectors concerning 2D.

The issue affects confidentiality, integrity, and availability. It is related to vectors concerning Hotspot.

The XML parser in Expat does not use sufficient entropy for hash initialization, which allows context-dependent attackers to cause a denial of service (CPU consumption) via crafted identifiers in an XML document. This issue exists because of an incomplete fix for a previous vulnerability.

The issue is caused by an integer underflow in the `png check keyword` function in `pngwutil.c`, which allows remote attackers to have an unspecified impact via a space character as a keyword in a PNG image, triggering an out-of-bounds read. This could potentially affect the integrity, availability, and confidentiality of information. The vulnerability may be exploited by sending a specially crafted PNG image with a space character in the keyword.

The issue is related to a stack-based buffer overflow in the FascistGecosUser function, located in lib/fascist.c. This overflow can be triggered by a long GECOS field, which involves a long buffer. As a result, local users may cause a denial of service, leading to an application crash, or potentially gain privileges.

The issue is related to the parse reg exp function in the GNU C Library, which misparses alternatives. This can allow attackers to cause a denial of service, resulting in an assertion failure and application exit, or trigger an incorrect result by attempting a regular-expression match. The vulnerability is associated with data processing errors.