CVE-2013-5018

What it is

The is_asn1 function in strongSwan 4.1.11 through 5.0.4 does not properly validate the return value of the asn1_length function, which allows remote attackers to cause a denial of service (segmentation fault) via a (1) XAuth username, (2) EAP identity, or (3) PEM encoded file that starts with a 0x04, 0x30, or 0x31 character followed by an ASN.1 length value that triggers an integer overflow.

At a glance

Exploitability

Can be exploited over the network without logging in. Limited direct impact.

Exploit odds

3.0% chance of exploitation in the next 30 days (EPSS).

Fix

A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

1. 2013-08-28 23:55 UTC PublishedDisclosed publicly on CVE.org and NVD
2. 2026-06-16 23:58 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 3.0% in the next 30 days (EPSS).
• Severity: 4.3 MEDIUM (CVSS).
• Fix: a patch or advisory is linked.

Details

Published

2013-08-28 23:55 UTC

Last modified

2026-06-16 23:58 UTC

Exploit probability

3.0% · EPSS, next 30 days

Weakness

CWE-119 · Buffer errors

Record status

Modified

Affected

• Strongswan 4.1.11
• Strongswan 5.0.0
• Strongswan 5.0.1
• Strongswan 5.0.2
• Strongswan 5.0.3
• Strongswan 5.0.4
• Opensuse 11.4
• Opensuse 12.2

Attack profile CVSS 2.0 · 4.3

Attack vector

Network

Complexity

Medium

Authentication

None

Confidentiality

None

Integrity

None

Availability

Partial

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2013-5018.md and follow it. Check whether this project is affected by CVE-2013-5018. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge