Skip to content
Noroxi
CVE-2013-2054· NVD / CVE Program· CNA redhat

Buffer overflow in the atodn function in strongSwan 2.0.0 through 4.3.4, when Opportunistic Encryption is enabled and an RSA key is being us

Buffer overflow in the atodn function in strongSwan 2.0.0 through 4.3.4, 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-2053 and CVE-2013-2054.

MediumCVSS 5.1 · v2.0—No exploit Fix available
Published
Jul 9, 2013
Updated
Jun 16, 2026
EPSS
2.0% · 80th percentile
Follow this CVE

Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.

Report tools

JSON

Action score

21

Monitor

Low priority for now.

CVSS
20 / 40 · 5.1 / 10
CISA KEV
0 / 30 · Not listed
EPSS
1 / 30 · 2.0%

Noroxi analysis

No Noroxi analysis for this record yet

We don't hand-write analysis for the hundreds of thousands of vulnerabilities in the database; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.

We use this product, ask for help

Affected systems

VendorProduct
strongswanstrongswan

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • strongswan strongswan2.0.0
  • strongswan strongswan2.0.1
  • strongswan strongswan2.0.2
  • strongswan strongswan2.1.0
  • strongswan strongswan2.1.1
  • strongswan strongswan2.1.2
  • strongswan strongswan2.1.3
  • strongswan strongswan2.1.4
  • strongswan strongswan2.1.5
  • strongswan strongswan2.3.0
  • strongswan strongswan2.3.1
  • strongswan strongswan2.3.2
  • strongswan strongswan2.4
  • strongswan strongswan2.4.0
  • strongswan strongswan2.4.0a
  • strongswan strongswan2.4.1
  • strongswan strongswan2.4.2
  • strongswan strongswan2.4.3
  • strongswan strongswan2.4.4
  • strongswan strongswan2.5.0

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12strongswanbefore 4.3.4-14.3.4-1

Other highest-scoring records for the same primary product.

  • CVE-2023-41913strongSwan before 5.9.12 has a buffer overflow and possible unauthenticated remote code execution via a DH public value that exceeds the int
    40Plan
  • CVE-2023-26463strongSwan 5.9.8 and 5.9.9 potentially allows remote code execution because it uses a variable named "public" for two different purposes wit
    40Plan
  • CVE-2015-3991strongSwan 5.2.2 and 5.3.0 allows remote attackers to cause a denial of service (daemon crash) or execute arbitrary code.
    40Plan
  • CVE-2021-45079In strongSwan before 5.9.5, a malicious responder can send an EAP-Success message too early without actually authenticating the client and (
    37Monitor
  • CVE-2026-25075strongSwan 4.5.0 < 6.0.5 EAP-TTLS AVP Parsing Integer Underflow
    34Monitor
  • CVE-2025-62291In the eap-mschapv2 plugin (client-side) in strongSwan before 6.0.3, a malicious EAP-MSCHAPv2 server can send a crafted message of size 6 th
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:strongswan4.3.4-1 · Debian:12Package 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.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

No nightly-computed relations.

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Special conditions such as timing or configuration are required.

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
High
Confidentiality impact
P
Integrity impact
P
Availability impact
P

CVSS vector

AV:N/AC:H/Au:N/C:P/I:P/A:P

nvd-primary

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

All records