CVE-2019-12521Not scoredCWE-193

CVE-2019-12521: Squid-Cache vulnerability

Squid-Cache · Squid

Vendor fix available · Affected: Squid-Cache · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

5.9%probability of exploitation in the next 30 days

93rd percentile

050100

Higher than 93% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

An issue was discovered in Squid through 4.7. When Squid is parsing ESI, it keeps the ESI elements in ESIContext. ESIContext contains a buffer for holding a stack of ESIElements. When a new ESIElement is parsed, it is added via addStackElement. addStackElement has a check for the number of elements in this buffer, but it's off by 1, leading to a Heap Overflow of 1 element. The overflow is within the same structure so it can't affect adjacent memory blocks, and thus just leads to a crash while processing.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Off-by-one Error · Memory Corruption
Vendor: Squid-Cache
Published: April 2020
Band: Possible (1 to 10%), April 2020

CoverageNo articles yet

No CyberSIXT article names CVE-2019-12521 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.