LiveActive security incident?Get immediate response
CVE Record

CVE-2021-38614: Polipo through 1.1.1, when NDEBUG is used, allows a heap-based buffer overflow during parsing of a Range he...

Polipo through 1.1.1, when NDEBUG is used, allows a heap-based buffer overflow during parsing of a Range header. NOTE: This vulnerability only affects products that are no longer supported by the maintainer

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2021-38614 is a denial-of-service risk in unsupported Polipo proxy versions through 1.1.1. A specially malformed Range header can trigger a heap buffer overflow when the software was built with NDEBUG, potentially crashing the service.

Executive priority

Prioritize removal or containment if Polipo is internet-facing or used by untrusted clients. The product is no longer maintainer-supported, making long-term remediation a replacement decision rather than a routine patch cycle.

Technical view

The issue is a CWE-787 heap-based buffer overflow in Polipo Range header parsing, conditional on NDEBUG builds. CVSS 3.1 is 7.5: network reachable, low complexity, no privileges, no user interaction, with availability impact only.

Likely exposure

Exposure is most likely in legacy environments still running Polipo through 1.1.1. The source bundle does not provide CPEs, package names, or supported downstream product mappings, so inventory confirmation is required.

Exploitation context

The bundle does not show CISA KEV listing or any cited active exploitation evidence. The issue is remotely reachable if Polipo accepts untrusted HTTP proxy traffic, but public exploit status is not established here.

Researcher notes

Evidence supports availability impact from Range header parsing in NDEBUG builds. The affected-product metadata is incomplete in the bundle, and no official fix is named. Avoid assuming impact beyond Polipo through 1.1.1 without local build and package evidence.

Mitigation direction

  • Retire or replace unsupported Polipo where possible.
  • Check operating system or package maintainer guidance for available downstream fixes.
  • Restrict Polipo access to trusted networks only.
  • Treat NDEBUG-built Polipo through 1.1.1 as affected until proven otherwise.
  • Monitor for unexpected Polipo crashes or restarts.

Validation and detection

  • Inventory hosts for Polipo installations and versions through 1.1.1.
  • Confirm whether deployed binaries were built with NDEBUG.
  • Review network paths exposing Polipo to untrusted clients.
  • Check service logs and supervisors for crash patterns.
  • Document unsupported instances for replacement planning.
Prepared
Confidence
medium
Sources
3

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.

cwe · low confidence lookup

CWE-787: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2021-38614 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
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

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.

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

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2021-38614Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-787 · source CWE mapping

Out-of-bounds Write

Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.