# CVE-2013-1752: Various versions of Python do not properly restrict readline calls, which allows remote attackers to cause a denial of service (memory consu


- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 3 Jun 2019
- **Updated:** 3 Jun 2019
- **Also known as:** PSF-2019-1, UBUNTU-CVE-2013-1752

## What is CVE-2013-1752?

CVE-2013-1752 is a vulnerability, published on 3 Jun 2019. 

### Official description

Various versions of Python do not properly restrict readline calls, which allows remote attackers to cause a denial of service (memory consumption) via a long string, related to (1) httplib - fixed in 2.7.4, 2.6.9, and 3.3.3; (2) ftplib - fixed in 2.7.6, 2.6.9, 3.3.3; (3) imaplib - not yet fixed in 2.7.x, fixed in 2.6.9, 3.3.3; (4) nntplib - fixed in 2.7.6, 2.6.9, 3.3.3; (5) poplib - not yet fixed in 2.7.x, fixed in 2.6.9, 3.3.3; and (6) smtplib - not yet fixed in 2.7.x, fixed in 2.6.9, not yet fixed in 3.3.x. NOTE: this was REJECTed because it is incompatible with CNT1 "Independently Fixable" in the CVE Counting Decisions

## Which versions are affected by CVE-2013-1752?


## How do I fix CVE-2013-1752?

Upgrade to a fixed version.

## Is CVE-2013-1752 being exploited?

There is no known exploitation of CVE-2013-1752 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-1752 and fix it if it is affected.

What it is: CVE-2013-1752 is a vulnerability, published on 3 Jun 2019. 
Exploitation: There is no known exploitation of CVE-2013-1752 in the wild and no public exploit code.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2013-1752/ (Markdown: https://insights.sbomify.com/CVE-2013-1752/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2013-1752
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2013-1752
- OSV: https://osv.dev/vulnerability/CVE-2013-1752

---
From sbomify Insights: https://insights.sbomify.com/CVE-2013-1752/
Summaries are generated and may contain mistakes; the official description above is the record.