CVE-2013-2053: Buffer overflow in the atodn function in Openswan before 2.6.39, when Opportunistic Encryption is enabled and an RSA key is being used…
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 2.4% (FIRST EPSS); higher than 84.6% of all records.
- Fixed version: openswan (Debian:6.0) 1:2.6.28+dfsg-5+squeeze2; openswan (Debian:7) 1:2.6.37-3+deb7u1; openswan (Red Hat:enterprise_linux:5::server) 0:2.6.32-5.el5_9.
Low priority for now. Upgrade to openswan (Debian:6.0) 1:2.6.28+dfsg-5+squeeze2; openswan (Debian:7) 1:2.6.37-3+deb7u1; openswan (Red Hat:enterprise_linux:5::server) 0:2.6.32-5.el5_9 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Jul 9, 2013
- Updated
- Jun 16, 2026
- EPSS
- 2.4% · 84th percentile
- CWE
- CWE-119
Report tools
Action score
28
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 2.4%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| xelerance | openswan | cpe:2.3:a:xelerance:openswan |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- xelerance openswanup to 2.6.38 inclusive
- xelerance openswan2.6.01
- xelerance openswan2.6.02
- xelerance openswan2.6.03
- xelerance openswan2.6.04
- xelerance openswan2.6.05
- xelerance openswan2.6.06
- xelerance openswan2.6.07
+12 more rows
- xelerance openswan2.6.08
- xelerance openswan2.6.09
- xelerance openswan2.6.10
- xelerance openswan2.6.11
- xelerance openswan2.6.12
- xelerance openswan2.6.13
- xelerance openswan2.6.14
- xelerance openswan2.6.15
- xelerance openswan2.6.16
- xelerance openswan2.6.17
- xelerance openswan2.6.18
- xelerance openswan2.6.19
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:6.0 | openswan | before 1:2.6.28+dfsg-5+squeeze2 | 1:2.6.28+dfsg-5+squeeze2 |
| Debian:7 | openswan | before 1:2.6.37-3+deb7u1 | 1:2.6.37-3+deb7u1 |
| Red Hat:enterprise_linux:5::server | openswan | before 0:2.6.32-5.el5_9 | 0:2.6.32-5.el5_9 |
| Red Hat:enterprise_linux:5::server | openswan-debuginfo | before 0:2.6.32-5.el5_9 | 0:2.6.32-5.el5_9 |
| Red Hat:enterprise_linux:5::server | openswan-doc | before 0:2.6.32-5.el5_9 | 0:2.6.32-5.el5_9 |
| Red Hat:enterprise_linux:6::client | openswan | before 0:2.6.32-20.el6_4 | 0:2.6.32-20.el6_4 |
| Red Hat:enterprise_linux:6::client | openswan-debuginfo | before 0:2.6.32-20.el6_4 | 0:2.6.32-20.el6_4 |
| Red Hat:enterprise_linux:6::client | openswan-doc | before 0:2.6.32-20.el6_4 | 0:2.6.32-20.el6_4 |
Same product
xelerance: all recordsOther highest-scoring records for the same primary product.
- CVE-2018-15836In verify_signed_hash() in lib/liboswkeys/signatures.c in Openswan before 2.6.50.1, the RSA implementation does not verify the value of…30Monitor
- CVE-2010-3753programs/pluto/xauth.c in the client in Openswan 2.6.26 through 2.6.28 allows remote authenticated gateways to execute arbitrary commands…27Monitor
- CVE-2010-3752programs/pluto/xauth.c in the client in Openswan 2.6.25 through 2.6.28 allows remote authenticated gateways to execute arbitrary commands…27Monitor
Published before and after this one in the same product
- ← EarlierCVE-2011-3380Nov 17, 2011 · Openswan 2.6.29 through 2.6.35 allows remote attackers to cause a denial of service (NULL pointer dereference and pluto IKE daemon crash)…21Monitor
- ← EarlierCVE-2011-4073Nov 17, 2011 · Use-after-free vulnerability in the cryptographic helper handler functionality in Openswan 2.3.0 through 2.6.36 allows remote authenticated…17Monitor
- Later →CVE-2013-6466Jan 26, 2014 · Openswan 2.6.39 and earlier allows remote attackers to cause a denial of service (NULL pointer dereference and IKE daemon restart) via…21Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:openswan | 1:2.6.28+dfsg-5+squeeze2 · Debian:6.0 | Package registry (OSV) |
| red hat:openswan | 0:2.6.32-5.el5_9 · Red Hat:enterprise_linux:5::server | Package registry (OSV) |
| red hat:openswan-debuginfo | 0:2.6.32-5.el5_9 · Red Hat:enterprise_linux:5::server | Package registry (OSV) |
| red hat:openswan-doc | 0:2.6.32-5.el5_9 · Red Hat:enterprise_linux:5::server | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (6 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.