Python 2.6.8/2.7.6/3.3.2 poplib readline memory allocation

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.
7.2$0-$5k0.00

Summaryinfo

A vulnerability identified as problematic has been detected in Python 2.6.8/2.7.6/3.3.2. This affects the function readline of the component poplib. This manipulation causes memory allocation. The identification of this vulnerability is CVE-2013-1752. There is no exploit available. You should upgrade the affected component.

Detailsinfo

A vulnerability classified as critical was found in Python 2.6.8/2.7.6/3.3.2 (Programming Language Software). Affected by this vulnerability is the function readline of the component poplib. The manipulation with an unknown input leads to a memory allocation vulnerability. The CWE definition for the vulnerability is CWE-789. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. As an impact it is known to affect availability.

The weakness was shared 09/25/2012 by Christian Heimes with OUSPG as Issue16041 as confirmed bug report (Website). The advisory is shared at bugs.python.org. This vulnerability is known as CVE-2013-1752 since 02/15/2013. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details are known, but no exploit is available. The advisory points out:

An erroneous or malicious POP3 server can trick the poplib module to consume large amounts of memory.

The vulnerability scanner Nessus provides a plugin with the ID 75315 (openSUSE Security Update : python3 (openSUSE-SU-2014:0498-1)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family SuSE Local Security Checks and running in the context l. The commercial vulnerability scanner Qualys is able to test this issue with plugin 350081 (Amazon Linux Security Advisory for python26: ALAS-2015-621).

Upgrading to version 2.6.9 or 3.3.3 eliminates this vulnerability. The upgrade is hosted for download at hg.python.org. A possible mitigation has been published 6 months after the disclosure of the vulnerability. The bug report contains the following remark:

The poplib module should be modified to use limited readline() with _MAXLINE like the httplib module. RFC 1939 says: "Responses in the POP3 consist of a status indicator and a keyword possibly followed by additional information. All responses are terminated by a CRLF pair. Responses may be up to 512 characters long, including the terminating CRLF." It doesn't say anything about the length of a line in a multi-line response. It's reasonable to belief that 512 octets are valid, too. We could quadruple the limit to 2048 in order to be safe.

The vulnerability is also documented in the databases at Tenable (75315), SecurityFocus (BID 61050†) and OSVDB (101382†). The entries VDB-11628, VDB-11630, VDB-11631 and VDB-11632 are related to this item. If you want to get the best quality for vulnerability data then you always have to consider VulDB.

Productinfo

Type

Name

Version

License

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 7.5
VulDB Meta Temp Score: 7.2

VulDB Base Score: 7.5
VulDB Temp Score: 7.2
VulDB Vector: 🔍
VulDB Reliability: 🔍

CVSSv2info

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

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

Exploitinginfo

Class: Memory allocation
CWE: CWE-789 / CWE-400 / CWE-404
CAPEC: 🔍
ATT&CK: 🔍

Physical: No
Local: No
Remote: Yes

Availability: 🔍
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔍

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Nessus ID: 75315
Nessus Name: openSUSE Security Update : python3 (openSUSE-SU-2014:0498-1)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Context: 🔍
Nessus Port: 🔍

OpenVAS ID: 65811
OpenVAS Name: VMSA-2014-0012: VMware vSphere product updates address security vulnerabilities
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: 🔍

Upgrade: Python 2.6.9/3.3.3

Timelineinfo

09/25/2012 🔍
02/15/2013 +143 days 🔍
02/23/2013 +8 days 🔍
07/09/2013 +136 days 🔍
12/27/2013 +171 days 🔍
12/27/2013 +0 days 🔍
06/13/2014 +167 days 🔍

Sourcesinfo

Advisory: Issue16041
Researcher: Christian Heimes
Organization: OUSPG
Status: Confirmed

CVE: CVE-2013-1752 (🔍)
GCVE (CVE): GCVE-0-2013-1752
GCVE (VulDB): GCVE-100-11629

OVAL: 🔍

SecurityFocus: 61050 - Google Chrome CVE-2013-2877 Out of Bounds Denial of Service Vulnerability
OSVDB: 101382

See also: 🔍

Entryinfo

Created: 12/27/2013 18:15
Changes: 12/27/2013 18:15 (73)
Complete: 🔍
Cache ID: 216:8F3: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 ▸

Interested in the pricing of exploits?

See the underground prices here!