CVE-2024-4141 Out-of-bounds array write in Xpdf 4.05 due to incorrect bounds check

Out-of-bounds array write in Xpdf 4.05 and earlier, triggered by an invalid character code in a Type 1 font. The root problem was a bounds check that was being optimized away by modern compilers...

CVE-2024-4141

Removed by vendor...

CVE-2024-4141

Out-of-bounds array write in Xpdf 4.05 and earlier, triggered by an invalid character code in a Type 1 font. The root problem was a bounds check that was being optimized away by modern compilers...

CVE-2024-4141 Out-of-bounds array write in Xpdf 4.05 due to incorrect bounds check

Out-of-bounds array write in Xpdf 4.05 and earlier, triggered by an invalid character code in a Type 1 font. The root problem was a bounds check that was being optimized away by modern compilers...

CVE-2024-4141

CVE-2024-4141: Out-of-bounds array write in Xpdf 4.05 and earlier caused by a bounds-check optimization bug in Type 1 font handling. The Fedora advisories indicate the issue is addressed by updating to xpdf 4.06 (Fedora 42/43 packages), which fixes the vulnerable code path. The CVE description no...

Xpdf 缓冲区错误漏洞

Xpdf is a free PDF viewer and toolkit from Xpdf, Inc. that includes a text extractor, image converter, HTML converter, and more. A security vulnerability exists in Xpdf versions 4.05 and earlier, which stems from a vulnerability that allows an attacker to trigger an out-of-bounds array write...

CVE-2024-3900

Out-of-bounds array write in Xpdf 4.05 and earlier, triggered by long Unicode sequence in ActualText...

CVE-2024-3900

Out-of-bounds array write in Xpdf 4.05 and earlier, triggered by long Unicode sequence in ActualText...

CVE-2024-3900

Out-of-bounds array write in Xpdf 4.05 and earlier, triggered by long Unicode sequence in ActualText...

UBUNTU-CVE-2024-3900

Out-of-bounds array write in Xpdf 4.05 and earlier, triggered by long Unicode sequence in ActualText...

CVE-2024-3900

CVE-2024-3900 affects Xpdf up to version 4.05. The issue is an out-of-bounds array write triggered by a long Unicode sequence in ActualText, resulting in an availability impact. Fedora advisories and Slackware/Nessus entries indicate the remediation is to upgrade to xpdf 4.06 or newer; Fedora 42/...

CVE-2024-3900 Out-of-bounds stack array write in Xpdf 4.05 due to missing zero check

Out-of-bounds array write in Xpdf 4.05 and earlier, triggered by long Unicode sequence in ActualText...

CVE-2024-3900

Removed by vendor...

CVE-2024-3900

Out-of-bounds array write in Xpdf 4.05 and earlier, triggered by long Unicode sequence in ActualText...

CVE-2024-3900 Out-of-bounds stack array write in Xpdf 4.05 due to missing zero check

Out-of-bounds array write in Xpdf 4.05 and earlier, triggered by long Unicode sequence in ActualText...

PT-2024-28315

Name of the Vulnerable Software and Affected Versions Xpdf versions 4.05 and earlier Description The issue is an out-of-bounds array write triggered by a long Unicode sequence in ActualText. This can potentially lead to exploitation. Recommendations For Xpdf versions 4.05 and earlier, consider...

Xpdf 缓冲区错误漏洞

Xpdf is a free PDF viewer and toolkit from Xpdf, including a text extractor, image converter, HTML converter, and more. A security vulnerability exists in Xpdf versions 4.05 and earlier, which stems from a long Unicode sequence in ActualText that could result in out-of-bounds array writes...

Denial Of Service (DoS)

Xpdf is vulnerable to Denial of Service DoS. The vulnerability is due to the TextLine class mishandling characters with large y coordinates, potentially leading to a Denial of Service DoS or other unspecified impacts...

Excessive Memory Allocation (Throttling)

xpdf is vulnerable to Excessive Memory AllocationThrottling. The vulnerability is due to insufficient input validation, which allows crafted input to trigger excessive memory allocation. For example, sending a crafted PDF document to the pdftoppm binary can exploit this vulnerability, particularl...

NULL Pointer Dereference

XPDF is vulnerable to a Null Pointer Dereference. The vulnerability is due to unhandled null pointer dereference, occurring at line 2393 in the FoFiType1C.cc file...