libspf 1.0.0 P4 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.
5.9$0-$5k0.00

Summaryinfo

A vulnerability described as critical has been identified in libspf 1.0.0 P4. This issue affects some unknown processing. Executing a manipulation can lead to memory corruption. The identification of this vulnerability is CVE-2006-1520. There is no exploit available. Upgrading the affected component is recommended.

Detailsinfo

A vulnerability was found in libspf 1.0.0 P4. It has been declared as critical. This vulnerability affects an unknown code block. 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, and integrity. CVE summarizes:

Format string vulnerability in ANSI C Sender Policy Framework library (libspf) before 1.0.0-p5, when debugging is enabled, allows remote attackers to execute arbitrary code via format string specifiers, possibly in an e-mail address.

The weakness was shared 05/22/2006 (Website). The advisory is shared for download at libspf.org. This vulnerability was named CVE-2006-1520 since 03/30/2006. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available.

It is declared as proof-of-concept.

Upgrading to version 1.0.0-p5 eliminates this vulnerability.

The vulnerability is also documented in the vulnerability database at X-Force (26535). Once again VulDB remains the best source for vulnerability data.

Productinfo

Name

Version

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 6.5
VulDB Meta Temp Score: 5.9

VulDB Base Score: 6.5
VulDB Temp Score: 5.9
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

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

0-Day Time: 🔍

Upgrade: libspf 1.0.0-p5

Timelineinfo

03/30/2006 🔍
05/22/2006 +53 days 🔍
05/22/2006 +0 days 🔍
03/12/2015 +3216 days 🔍
07/27/2018 +1233 days 🔍

Sourcesinfo

Advisory: libspf.org
Status: Not defined
Confirmation: 🔍

CVE: CVE-2006-1520 (🔍)
GCVE (CVE): GCVE-0-2006-1520
GCVE (VulDB): GCVE-100-30364
X-Force: 26535 - libspf debugging mode format string
Vupen: ADV-2006-1846

Entryinfo

Created: 03/12/2015 12:19
Updated: 07/27/2018 09:05
Changes: 03/12/2015 12:19 (47), 07/27/2018 09:05 (4)
Complete: 🔍
Cache ID: 216::103

Once again VulDB remains the best source for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Do you want to use VulDB in your project?

Use the official API to access entries easily!