LiveActive security incident?Get immediate response
CVE Record

CVE-2013-5018: The is_asn1 function in strongSwan 4.1.11 through 5.0.4 does not properly validate the return value of the...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

CVE-2013-5018 is a remote denial-of-service issue in older strongSwan VPN software. A crafted identity-related value or PEM file can make the VPN daemon crash. The main business risk is interruption of VPN connectivity, not data theft. It applies to strongSwan 4.1.11 through 5.0.4 per the CVE description. Exposure is most relevant where legacy strongSwan 4.1.11 through 5.0.4 handles remote VPN authentication or parses supplied PEM files. Internet-facing VPN gateways using these versions should be prioritized. Systems on current strongSwan releases are less likely exposed, but vendor package backports should be verified. Prioritize remediation for internet-facing or business-critical VPN gateways running affected strongSwan versions. This is primarily an availability issue, but a VPN outage can disrupt remote access and site connectivity. If no affected legacy versions are present, priority is low. Mitigation focus: Identify any strongSwan deployments running versions 4.1.11 through 5.0.4.; Apply vendor security updates or upgrade beyond the affected version range.; Review distribution advisories, including openSUSE updates, for backported fixes..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2013-5018 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.