CVE-2022-31560
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 uncleYiba/photo_tag repository through 2020-08-31 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 uncleYiba/photo_tag Flask application contains an absolute path traversal vulnerability due to unsafe use of Flask's send_file function. An attacker can manipulate file paths to access sensitive system files outside the intended directory, potentially reading configuration files, credentials, or other sensitive 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<= 2020-08-31CVSS 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 photo_tag Flask app is deployedSearch for files named 'photo_tag' or directories containing 'photo_tag' in your web application directory. Check your web server configuration (Apache/Nginx) for aliases or reverse proxies pointing to a Flask application with 'photo_tag' in the path.Affected if The photo_tag Flask application is present in your environment
-
Determine the application version or installation dateCheck the installation date or version of the photo_tag project by inspecting the application's source code files, setup.py, requirements.txt, or git history. Look for any version markers or commit dates.Affected if The installation date is on or before 2020-08-31, or the version is <= the 2020-08-31 release
-
Locate the vulnerable send_file usageSearch the application source code for usage of Flask's send_file function, particularly in routes that handle image/file downloads or display functionality.Affected if Code contains send_file() calls handling user-supplied path parameters without path validation
-
Check if file parameter is user-controlledExamine the route handlers using send_file - identify if the file path comes directly from request parameters (like request.args.get or request.form.get) without sanitization.Affected if The file/path parameter passed to send_file originates directly from user input without validation
-
Inspect path validation logicReview the code around send_file calls for any path sanitization using os.path.abspath, os.path.dirname, or allowlist validation. Look for whether the resolved path is checked to remain within an intended directory.Affected if No path validation is performed, or validation exists but can be bypassed, before passing the path to send_file
You are affected if the photo_tag Flask application is deployed with a version or installation date on or before 2020-08-31 and the code uses send_file with user-controlled file paths without proper path 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 dataSanitize and validate all user-controlled file paths before passing them to send_file. Use os.path functions (such as os.path.abspath and os.path.dirname) to ensure the resolved path remains within the intended directory, and implement allowlist validation for accessible files.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-31560 — 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-31560 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