LiveActive security incident?Get immediate response
CVE Record

CVE-2021-32754: Improper Restriction of XML External Entity Reference in de.tud.sse

FlowDroid is a data flow analysis tool. FlowDroid versions prior to 2.9.0 contained an XML external entity (XXE) vulnerability that allowed an attacker who had control over the source/sink definition file in XML format to read files from external locations. In order for this to occur, the XML-based format for sources and sinks had to be used and the attacker had to able control the source/sink definition file. The vulnerability was patched in version 2.9.0. As a workaround, do not allow untrusted entities to control the source/sink definition file.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

FlowDroid before 2.9.0 could expose local or external files when it processed an attacker-controlled XML source/sink definition file. The risk is mainly to teams running FlowDroid in analysis pipelines that accept untrusted definitions, not to typical public-facing systems.

Executive priority

Treat as a moderate-priority tooling risk. It should be remediated during normal vulnerability management, with faster action where FlowDroid processes untrusted project inputs or runs with access to sensitive files.

Technical view

CVE-2021-32754 is a CWE-611 XXE flaw in FlowDroid XML source/sink definition handling. Exploitation requires the XML-based format and attacker control over the source/sink definition file. The stated impact is confidentiality loss through file reads from external locations.

Likely exposure

Exposure is most likely in developer, research, CI, or security analysis environments using FlowDroid versions earlier than 2.9.0 with XML source/sink definitions from users, repositories, or third parties.

Exploitation context

The source bundle does not show CISA KEV listing or active exploitation evidence. The attack prerequisites are specific: XML source/sink format must be used, and the attacker must control that definition file.

Researcher notes

No CPEs were supplied in the bundle. Validate local package names and coordinates against FlowDroid usage. The available evidence supports affected versions before 2.9.0, confidentiality impact, and the vendor workaround only.

Mitigation direction

  • Upgrade FlowDroid to version 2.9.0 or later.
  • Do not allow untrusted entities to control source/sink definition files.
  • Inventory CI and analysis pipelines that run FlowDroid.
  • Check the vendor advisory for any updated guidance.

Validation and detection

  • Identify FlowDroid versions in dependency files, containers, and analysis tooling.
  • Confirm whether XML source/sink definition files are used.
  • Review who can submit or modify source/sink definition files.
  • Verify FlowDroid is 2.9.0 or later, or untrusted control is blocked.
Prepared
Confidence
high
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-611: 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-32754 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

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
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N1.63.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2021-32754Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
secure-software-engineeringFlowDroid< 2.9.0Listed
Weakness

CWE details

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

CWE-611 · source CWE mapping

Improper Restriction of XML External Entity Reference

Improper Restriction of XML External Entity Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.