CVE-2021-28172
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThere is a Path Traversal vulnerability in the file download function of Vangene deltaFlow E-platform. Remote attackers can access credential data with this leakage.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidencePath Traversal vulnerability in Vangene deltaFlow E-platform's file download function allows remote attackers to manipulate file path parameters to access sensitive files outside the intended directory, including credential data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 4.0, < 7.7CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm Deltaflow installationIdentify if Vangene Deltaflow E-platform is installed in your environment. Look for Deltaflow-related services, applications, or web interfaces.Affected if Deltaflow is present and running in the environment
-
Check Deltaflow versionLocate and retrieve the installed version of Deltaflow (Deltaflow Project Deltaflow). This may be found in the application UI, configuration files, or system inventory. Compare your version against the affected range: 4.0 through versions less than 7.7.Affected if Installed version is >= 4.0 and < 7.7
-
Identify file download function exposureDetermine if the file download functionality is accessible. This may be a web endpoint, API, or application feature that accepts file path parameters for downloading files.Affected if The file download function is exposed and accessible to users or attackers
-
Check for sensitive file accessibilityInspect whether the file download function can be manipulated to access files outside the intended directory. Test or review if path traversal sequences (such as ../) can be used in file path parameters to access system files or credential stores.Affected if The download function allows path traversal and can access files outside the intended directory, including credential data
You are affected if Deltaflow version is >= 4.0 and < 7.7 AND the file download function is accessible and permits path traversal to reach sensitive files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data7.7
Implement strict input validation and canonical path checking on file path parameters in the download function; restrict file access to allowed directories and use whitelisting for permitted file paths.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28172 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-28172 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data