GNU Enscript 1.6.1/1.6.4 read_special_escape memory corruption

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
9.0$0-$5k0.00

Summaryinfo

A vulnerability was found in GNU Enscript 1.6.1/1.6.4. It has been classified as critical. Affected by this vulnerability is the function read_special_escape. The manipulation leads to memory corruption. This vulnerability is listed as CVE-2008-3863. There is no available exploit. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in GNU Enscript 1.6.1/1.6.4. It has been rated as critical. This issue affects the function read_special_escape. The manipulation with an unknown input leads to a memory corruption vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. The summary by CVE is:

Stack-based buffer overflow in the read_special_escape function in src/psgen.c in GNU Enscript 1.6.1 and 1.6.4 beta, when the -e (aka special escapes processing) option is enabled, allows user-assisted remote attackers to execute arbitrary code via a crafted ASCII file, related to the setfilename command.

The bug was discovered 10/22/2008. The weakness was presented 10/23/2008 by Ulf Harnhammar with Secunia Research (Website). The advisory is shared at us-cert.gov. The identification of this vulnerability is CVE-2008-3863 since 08/29/2008. The exploitation is known to be difficult. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details are known, but no exploit is available.

It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 1 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 67773 (Oracle Linux 3 / 4 : enscript (ELSA-2008-1021)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Oracle Linux Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 117208 (CentOS Security Update for enscript (CESA-2008:1016)).

Upgrading eliminates this vulnerability. A possible mitigation has been published 2 months after the disclosure of the vulnerability.

The vulnerability is also documented in the databases at X-Force (46026), Tenable (67773), SecurityFocus (BID 31858†), OSVDB (49224†) and Secunia (SA32137†). See VDB-3978, VDB-23858, VDB-30376 and VDB-40710 for similar entries. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

License

Website

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 10.0
VulDB Meta Temp Score: 9.0

VulDB Base Score: 10.0
VulDB Temp Score: 9.0
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍

NVD Base Score: 🔍

Exploitinginfo

Class: Memory corruption
CWE: CWE-119
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Proof-of-Concept

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 67773
Nessus Name: Oracle Linux 3 / 4 : enscript (ELSA-2008-1021)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 61933
OpenVAS Name: Debian Security Advisory DSA 1670-1 (enscript)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍

Timelineinfo

08/29/2008 🔍
10/22/2008 +54 days 🔍
10/22/2008 +0 days 🔍
10/22/2008 +0 days 🔍
10/23/2008 +1 days 🔍
10/23/2008 +0 days 🔍
11/10/2008 +18 days 🔍
12/15/2008 +35 days 🔍
07/12/2013 +1670 days 🔍
03/17/2015 +613 days 🔍
08/20/2019 +1617 days 🔍

Sourcesinfo

Vendor: gnu.org

Advisory: us-cert.gov
Researcher: Ulf Harnhammar
Organization: Secunia Research
Status: Not defined
Confirmation: 🔍

CVE: CVE-2008-3863 (🔍)
GCVE (CVE): GCVE-0-2008-3863
GCVE (VulDB): GCVE-100-44693

OVAL: 🔍

X-Force: 46026
SecurityFocus: 31858 - GNU Enscript 'src/psgen.c' Stack Based Buffer Overflow Vulnerability
Secunia: 32137
OSVDB: 49224 - CVE-2008-3863 - GNU - Enscript - Buffer Overflow Issue
Vulnerability Center: 19965 - GNU Enscript 1.6.1 and 1.6.4 beta Buffer Overflow Allows Remote Code Execution via a ASCII File, Medium
Vupen: ADV-2008-2891

See also: 🔍

Entryinfo

Created: 03/17/2015 16:11
Updated: 08/20/2019 15:00
Changes: 03/17/2015 16:11 (77), 08/20/2019 15:00 (9)
Complete: 🔍
Cache ID: 216::103

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

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you need the next level of professionalism?

Upgrade your account now!