Strix
26.1K

CVE-2013-5018

UnknownEPSS 2.99%

Last modified

CVE-2013-5018 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 2.99% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability
2.99%

85.6th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
StrongswanStrongswan4.1.11
StrongswanStrongswan5.0.0
StrongswanStrongswan5.0.1
StrongswanStrongswan5.0.2
StrongswanStrongswan5.0.3
StrongswanStrongswan5.0.4
OpensuseOpensuse11.4
OpensuseOpensuse12.2
OpensuseOpensuse12.3

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is 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 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.
How severe is CVE-2013-5018?
Severity scoring for CVE-2013-5018 is pending analysis. The EPSS model estimates a 2.99% probability of exploitation in the next 30 days.
How do I fix CVE-2013-5018?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2013-5018?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST