CVE-2022-46309
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 · uneditedVitals ESP upload function has a path traversal vulnerability. A remote attacker with general user privilege can exploit this vulnerability to access arbitrary system files.
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 confidenceVitals ESP contains a path traversal vulnerability in its file upload function. An authenticated user with general privileges can manipulate file upload paths to escape the intended directory and read arbitrary system files on the host.
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>= 3.0.8, <= 6.2.0CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Identify Vitals ESP installation and versionLocate the Vitals ESP installation directory and find the version information file or system info page. Common locations include the main application directory or the administration interface.Affected if The installed version is >= 3.0.8 and <= 6.2.0
-
Confirm file upload functionality is accessibleLocate the file upload feature within the Vitals ESP web interface or API endpoints. Verify the upload functionality exists and is enabled for authenticated users.Affected if The file upload function is present and accessible to users with general/standard privileges (not just administrators)
-
Check for path traversal protection in upload handlingExamine the application's file upload handling code or configuration files. Look for input validation routines that sanitize or reject directory traversal sequences (such as ../ or ..\) in upload path parameters.Affected if No input validation exists, or the validation can be bypassed by manipulating the upload path parameter
-
Test if authenticated users can specify upload pathsUse an authenticated session with general user privileges to access the file upload function. Attempt to modify the upload path parameter to include traversal sequences and specify paths outside the intended upload directory.Affected if The application allows authenticated users to control or influence the upload path and does not properly restrict it to designated directories
A user is affected if they have Vitals ESP version 3.0.8 through 6.2.0 installed with the file upload feature accessible to authenticated users lacking proper path traversal protections.
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 dataImplement strict input validation on file upload paths, using allowlists and normalizing paths to prevent directory traversal sequences (../). Restrict upload operations to designated directories and verify file locations after upload.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46309 — 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-46309 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