CVE-2013-2053
Last modified
CVE-2013-2053 is a vulnerability of currently unknown severity. Buffer overflow in the atodn function in Openswan before 2.6.39, when Opportunistic Encryption is enabled and an RSA key is being used, allows remote attackers to cause a denial of service (pluto IKE daemon crash) and possibly execute arbitrary code via crafted DNS TXT records. NOTE: this might be the same vulnerability as CVE-2013-2052 and CVE-2013-2054.. EPSS estimates a 2.41% chance of exploitation in the next 30 days.
Description
Buffer overflow in the atodn function in Openswan before 2.6.39, when Opportunistic Encryption is enabled and an RSA key is being used, allows remote attackers to cause a denial of service (pluto IKE daemon crash) and possibly execute arbitrary code via crafted DNS TXT records. NOTE: this might be the same vulnerability as CVE-2013-2052 and CVE-2013-2054.
Metrics
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Xelerance | Openswan | <= 2.6.38 |
| Xelerance | Openswan | 2.6.01 |
| Xelerance | Openswan | 2.6.02 |
| Xelerance | Openswan | 2.6.03 |
| Xelerance | Openswan | 2.6.04 |
| Xelerance | Openswan | 2.6.05 |
| Xelerance | Openswan | 2.6.06 |
| Xelerance | Openswan | 2.6.07 |
| Xelerance | Openswan | 2.6.08 |
| Xelerance | Openswan | 2.6.09 |
| Xelerance | Openswan | 2.6.10 |
| Xelerance | Openswan | 2.6.11 |
| Xelerance | Openswan | 2.6.12 |
| Xelerance | Openswan | 2.6.13 |
| Xelerance | Openswan | 2.6.14 |
| Xelerance | Openswan | 2.6.15 |
| Xelerance | Openswan | 2.6.16 |
| Xelerance | Openswan | 2.6.17 |
| Xelerance | Openswan | 2.6.18 |
| Xelerance | Openswan | 2.6.19 |
| Xelerance | Openswan | 2.6.20 |
| Xelerance | Openswan | 2.6.21 |
| Xelerance | Openswan | 2.6.22 |
| Xelerance | Openswan | 2.6.23 |
| Xelerance | Openswan | 2.6.24 |
| Xelerance | Openswan | 2.6.25 |
| Xelerance | Openswan | 2.6.26 |
| Xelerance | Openswan | 2.6.27 |
| Xelerance | Openswan | 2.6.28 |
| Xelerance | Openswan | 2.6.29 |
| Xelerance | Openswan | 2.6.30 |
| Xelerance | Openswan | 2.6.31 |
| Xelerance | Openswan | 2.6.32 |
| Xelerance | Openswan | 2.6.33 |
| Xelerance | Openswan | 2.6.34 |
| Xelerance | Openswan | 2.6.35 |
| Xelerance | Openswan | 2.6.36 |
| Xelerance | Openswan | 2.6.37 |
References
- https://www.openswan.org/news/13Vendor Advisory
- https://www.openswan.org/news/13Vendor Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2013-2053?
How severe is CVE-2013-2053?
How do I fix CVE-2013-2053?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2013
- CVE-2013-2047The login page (aka index.php) in ownCloud before 5.0.6 does…
- CVE-2013-2048ownCloud before 5.0.6 does not properly check permissions, w…
- CVE-2013-2049Red Hat CloudForms 2 Management Engine (CFME) allows remote …
- CVE-2013-2050SQL injection vulnerability in the miq_policy controller in …
- CVE-2013-2051The Tomcat 6 DIGEST authentication functionality as used in …
- CVE-2013-2052Buffer overflow in the atodn function in libreswan 3.0 and 3…
- CVE-2013-2054Buffer overflow in the atodn function in strongSwan 2.0.0 th…
- CVE-2013-2055Unspecified vulnerability in Apache Wicket 1.4.x before 1.4.…
- CVE-2013-2056The Inter-Satellite Sync (ISS) operation in Red Hat Network …
- CVE-2013-2057YaBB through 2.5.2: 'guestlanguage' Cookie Parameter Local F…9.8
- CVE-2013-2058The host_start function in drivers/usb/chipidea/host.c in th…
- CVE-2013-2059OpenStack Identity (Keystone) Folsom 2012.2.4 and earlier, G…
Are you affected by CVE-2013-2053?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
