PyCrypto ARC2 2.0.1 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 PyCrypto ARC2 2.0.1. It has been rated as critical. This issue affects some unknown processing. This manipulation causes memory corruption. This vulnerability is handled as CVE-2009-0544. Additionally, an exploit exists. Upgrading the affected component is advised.

Detailsinfo

A vulnerability was found in PyCrypto ARC2 2.0.1. It has been declared as critical. Affected by this vulnerability is an unknown function. 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:

Buffer overflow in the PyCrypto ARC2 module 2.0.1 allows remote attackers to cause a denial of service and possibly execute arbitrary code via a large ARC2 key length.

The bug was discovered 02/06/2009. The weakness was released 02/12/2009 by Security Team (Mike) with Google Security Team (Website). The advisory is shared at openwall.com. This vulnerability is known as CVE-2009-0544 since 02/12/2009. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are unknown but a public exploit is available.

A public exploit has been developed in Python. It is possible to download the exploit at securityfocus.com. It is declared as proof-of-concept. The vulnerability was handled as a non-public zero-day exploit for at least 6 days. During that time the estimated underground price was around $0-$5k. The vulnerability scanner Nessus provides a plugin with the ID 38149 (Mandriva Linux Security Advisory : python-pycrypto (MDVSA-2009:050-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family Mandriva Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 116247 (Fedora Update for python-crypto (FEDORA-2009-1680)).

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

The vulnerability is also documented in the databases at X-Force (48617), Exploit-DB (32780), Tenable (38149), SecurityFocus (BID 33674†) and OSVDB (51958†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Vendor

Name

Version

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: 🔍
Access: Public
Status: Proof-of-Concept
Programming Language: 🔍
Download: 🔍

EPSS Score: 🔍
EPSS Percentile: 🔍

Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 38149
Nessus Name: Mandriva Linux Security Advisory : python-pycrypto (MDVSA-2009:050-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 63572
OpenVAS Name: Debian Security Advisory DSA 1726-1 (python-crypto)
OpenVAS File: 🔍
OpenVAS Family: 🔍

Qualys ID: 🔍
Qualys Name: 🔍

Exploit-DB: 🔍

Threat Intelligenceinfo

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

Countermeasuresinfo

Recommended: Upgrade
Status: 🔍

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

Timelineinfo

02/06/2009 🔍
02/06/2009 +0 days 🔍
02/07/2009 +1 days 🔍
02/12/2009 +5 days 🔍
02/12/2009 +0 days 🔍
02/12/2009 +0 days 🔍
02/23/2009 +11 days 🔍
03/01/2009 +6 days 🔍
03/09/2009 +8 days 🔍
04/23/2009 +45 days 🔍
03/17/2015 +2154 days 🔍
05/11/2025 +3708 days 🔍

Sourcesinfo

Advisory: openwall.com
Researcher: Security Team (Mike)
Organization: Google Security Team
Status: Confirmed
Confirmation: 🔍

CVE: CVE-2009-0544 (🔍)
GCVE (CVE): GCVE-0-2009-0544
GCVE (VulDB): GCVE-100-46501

OVAL: 🔍

X-Force: 48617
SecurityFocus: 33674 - PyCrypto ARC2 Module Buffer Overflow Vulnerability
Secunia: 34199 - Gentoo update for pycrypto, Highly Critical
OSVDB: 51958 - CVE-2009-0544 - PyCrypto - Buffer Overflow Issue
Vulnerability Center: 21077 - PyCrypto ARC2 Module 2.0.1 Buffer Overflow via a Large ARC2 Key Length, High

scip Labs: https://www.scip.ch/en/?labs.20161013

Entryinfo

Created: 03/17/2015 16:11
Updated: 05/11/2025 06:34
Changes: 03/17/2015 16:11 (79), 08/28/2019 16:18 (10), 12/23/2024 22:19 (18), 05/11/2025 06:34 (4)
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 want to use VulDB in your project?

Use the official API to access entries easily!