CVE-2022-31579
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 · uneditedThe ralphjzhang/iasset repository through 2022-05-04 on GitHub allows absolute path traversal because the Flask send_file function is used unsafely.
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 · moderate confidenceThe ralphjzhang/iasset Flask application suffers from an absolute path traversal vulnerability due to unsafe usage of Flask's send_file function. Attackers can manipulate file path requests to access arbitrary files on the server filesystem by providing absolute paths, bypassing directory containment. The CRITICAL CVSS score of 9.3 indicates ease of exploitation and complete confidentiality impact.
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<= 2022-05-04CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
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.
-
Identify if the iasset Flask application is installedLocate the application directory or check for the presence of the ralphjzhang/iasset project files in your environment. Common paths may include the web application root directory or Python site-packages.Affected if The iasset application files are present in your environment
-
Determine the installed version of iassetCheck the application version by inspecting version files, setup.py, requirements.txt, or the application's metadata. Compare your version against the affected range: versions dated 2022-05-04 or earlier.Affected if Your iasset version is dated 2022-05-04 or earlier, or if the version cannot be determined and the application is present
-
Inspect source code for unsafe send_file usageExamine the Flask application source code for calls to send_file that accept user-controlled path parameters without validation using safe_join or path allowlisting.Affected if The codebase contains send_file calls that process file path parameters without proper path validation or containment checks
-
Check if the vulnerable file endpoint is accessibleIdentify and test endpoints that handle file download or serving requests. Attempt to access known system files using absolute paths (for example, /etc/passwd on Linux or C:\Windows\System32\config\sam on Windows) through the application's file-serving functionality.Affected if The application accepts and processes absolute file paths through its file-serving endpoints, allowing access outside the intended directory
You are affected if the iasset application is present with a version dated 2022-05-04 or earlier and the application contains send_file functionality that processes file paths without proper validation.
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 dataReplace unsafe send_file calls with path validation using Flask's safe_join function or implement explicit allowlist checking to ensure requested files remain within the intended directory. Additionally, reject requests containing absolute paths or path traversal sequences (..).
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31579 — 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-2022-31579 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