Strix
26.1K

CVE-2005-1935

UnknownEPSS 26.63%

Last modified

CVE-2005-1935 is a vulnerability of currently unknown severity. Heap-based buffer overflow in the BERDecBitString function in Microsoft ASN.1 library (MSASN1.DLL) allows remote attackers to execute arbitrary code via nested constructed bit strings, which leads to a realloc of a non-null pointer and causes the function to overwrite previously freed memory, as demonstrated using a SPNEGO token with a constructed bit string during HTTP authentication, and a different vulnerability than CVE-2003-0818. NOTE: the researcher has claimed that MS:MS04-007 fixes this issue.. EPSS estimates a 26.63% chance of exploitation in the next 30 days.

Description

Heap-based buffer overflow in the BERDecBitString function in Microsoft ASN.1 library (MSASN1.DLL) allows remote attackers to execute arbitrary code via nested constructed bit strings, which leads to a realloc of a non-null pointer and causes the function to overwrite previously freed memory, as demonstrated using a SPNEGO token with a constructed bit string during HTTP authentication, and a different vulnerability than CVE-2003-0818. NOTE: the researcher has claimed that MS:MS04-007 fixes this issue.

Metrics

EPSS Probability
26.63%

97.8th percentile

Probability of exploitation in the next 30 days. Learn more

Affected Software

VendorProductVersionsUpdate
MicrosoftWindows 2000All versionsSp2
MicrosoftWindows 2003 Server64-bit—
MicrosoftWindows 2003 Serverr2—
MicrosoftWindows Nt4.0Sp6
MicrosoftWindows XpAll versions—

References

Timeline

Published
Last Modified
Status
Modified

Frequently Asked Questions

What is CVE-2005-1935?
Heap-based buffer overflow in the BERDecBitString function in Microsoft ASN.1 library (MSASN1.DLL) allows remote attackers to execute arbitrary code via nested constructed bit strings, which leads to a realloc of a non-null pointer and causes the function to overwrite previously freed memory, as demonstrated using a SPNEGO token with a constructed bit string during HTTP authentication, and a different vulnerability than CVE-2003-0818. NOTE: the researcher has claimed that MS:MS04-007 fixes this issue.
How severe is CVE-2005-1935?
Severity scoring for CVE-2005-1935 is pending analysis. The EPSS model estimates a 26.63% probability of exploitation in the next 30 days.
How do I fix CVE-2005-1935?
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-2005-1935?

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

Scan your code now

Source: NVD / NIST