LiveActive security incident?Get immediate response
CVE Record

CVE-2017-7376: Buffer overflow in libxml2 allows remote attackers to execute arbitrary code by leveraging an incorrect lim...

Buffer overflow in libxml2 allows remote attackers to execute arbitrary code by leveraging an incorrect limit for port values when handling redirects.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2017-7376 is a libxml2 buffer overflow tied to redirect handling. A remote attacker could potentially execute code if an affected application processes attacker-controlled input through the vulnerable path. The bundle does not provide CVSS, affected versions, or evidence of active exploitation.

Executive priority

Prioritize remediation for internet-facing or untrusted-content processing services. The business risk is potentially serious because the stated impact is remote code execution, but urgency is tempered by missing exploitation evidence and incomplete version data.

Technical view

The issue is described as an incorrect limit for port values when libxml2 handles redirects, leading to buffer overflow and possible arbitrary code execution. Upstream and Android patch references are listed, and Debian published DSA-3952. Version and CPE data are not provided in the bundle.

Likely exposure

Exposure is most likely in systems, applications, containers, or Android builds that include a vulnerable libxml2 and allow it to process untrusted XML or redirect-bearing resources. Confirm exposure through vendor package data, not the incomplete affected-product list here.

Exploitation context

The source bundle supports remote attack potential but does not show public exploit availability or active exploitation. CISA KEV status is false, so do not treat this as known exploited based on the provided evidence.

Researcher notes

Metadata is sparse: no CVSS, CWE, CPE, or affected version range is supplied. Use the upstream GNOME commit, Android patch, Debian DSA, and vendor bug tracking to build precise version mapping before declaring assets vulnerable or remediated.

Mitigation direction

  • Apply libxml2 updates from Debian, Android, upstream, or your platform vendor.
  • Inventory bundled libxml2 copies in applications, containers, firmware, and mobile builds.
  • Check vendor guidance where package versions differ from upstream libxml2 releases.
  • Limit untrusted XML processing and redirect handling until affected assets are patched.

Validation and detection

  • Confirm installed or bundled libxml2 versions against vendor advisories and patch references.
  • Review SBOMs and dependency manifests for direct or embedded libxml2 copies.
  • Verify Debian or Android security bulletin applicability for managed assets.
  • Document exceptions where version mapping cannot be proven from available sources.
Prepared
Confidence
medium
Sources
7

Public sources used

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-7376 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
6Source links

CVSS and timeline data

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

Source materials

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.