CVE-2022-31562
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 waveyan/internshipsystem repository through 2018-05-22 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 waveyan/internshipsystem Flask application contains an absolute path traversal vulnerability caused by unsafe usage of the send_file function. Attackers can manipulate file path parameters to access arbitrary files on the server filesystem outside the intended web root directory.
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<= 2018-05-22CVSS 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 internshipsystem Flask app is deployedSearch for files named 'internshipsystem' or a Flask application with 'waveyan' as the author/vendor in your environment, checking application directories, containers, or installed packagesAffected if The waveyan/internshipsystem application is present in your environment
-
Determine the application versionCheck the version metadata (setup.py, requirements.txt, git tags, or package.json) of the internshipsystem project and compare to the affected version date of 2018-05-22Affected if The installed version is dated on or before 2018-05-22
-
Locate send_file function usage in the codebaseSearch the application source code for occurrences of 'send_file' function calls, particularly in routes related to file download or viewing functionalityAffected if The send_file function is used within the application code
-
Identify user-controlled file path parametersExamine the send_file calls and their associated route handlers to determine if any path parameter comes from user input (request parameters, URL path segments) without validationAffected if File path parameters in send_file calls accept direct user input without sanitization
-
Test for path traversal vulnerabilityIf user input flows to send_file, attempt to access a known file outside the web root by providing path traversal sequences (e.g., ../../etc/passwd) as the file parameter valueAffected if The application returns file contents from paths outside the intended web root directory
You are affected if the internshipsystem Flask application is deployed with a version dated on or before 2018-05-22 and contains send_file calls that accept unsanitized user input for file path parameters.
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 validated paths that verify the requested file resides within an allowed directory, using techniques such as os.path.abspath() validation and path normalization checks before serving 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-31562 — 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-31562 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