Foo Labs Xpdf 4.00 JPXStream.cc JPXStream::readTilePart memory corruption

Summaryinfo

A vulnerability, which was classified as critical, has been found in Foo Labs Xpdf 4.00. Impacted is the function JPXStream::readTilePart of the file JPXStream.cc. This manipulation causes memory corruption. This vulnerability appears as CVE-2018-8100. The attack may be initiated remotely. There is no available exploit.

Detailsinfo

A vulnerability has been found in Foo Labs Xpdf 4.00 (Document Reader Software) and classified as critical. Affected by this vulnerability is the function JPXStream::readTilePart of the file JPXStream.cc. The manipulation with an unknown input leads to a memory corruption vulnerability. The CWE definition for the vulnerability is CWE-119. The product performs operations on a memory buffer, but it can read from or write to a memory location that is outside of the intended boundary of the buffer. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

The JPXStream::readTilePart function in JPXStream.cc in xpdf 4.00 allows attackers to launch denial of service (heap-based buffer overflow and application crash) or possibly have unspecified other impact via a specific pdf file, as demonstrated by pdftohtml.

The bug was discovered 02/22/2018. The weakness was presented 03/14/2018 (Website). The advisory is shared at forum.xpdfreader.com. This vulnerability is known as CVE-2018-8100 since 03/13/2018. The attack can be launched remotely. The exploitation doesn't need any form of authentication. It demands that the victim is doing some kind of user interaction. Technical details are known, but no exploit is available.

The vulnerability was handled as a non-public zero-day exploit for at least 19 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 232028 (Linux Distros Unpatched Vulnerability : CVE-2018-8100), which helps to determine the existence of the flaw in a target environment.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at Tenable (232028). See VDB-114494, VDB-114495, VDB-114496 and VDB-114497 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

• Document Reader Software

Vendor

• Foo Labs

Name

• Xpdf

Version

• 4.00

License

• open-source

CPE 2.3info

• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Discussion