CVE-2022-46899
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 · uneditedAn issue was discovered in Vocera Report Server and Voice Server 5.x through 5.8. There is Arbitrary File Upload. The BaseController class, that each of the service controllers derives from, allows for the upload of arbitrary files. If the HTTP request is a multipart/form-data POST request, any parameters with a filename entry will have their content written to a file in the Vocera upload-staging directory with the specified filename in the parameter.
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 confidenceThe BaseController class in Vocera Report Server and Voice Server 5.x through 5.8 does not validate uploaded filenames or file types in multipart/form-data POST requests, allowing attackers to write arbitrary files to the upload-staging directory with user-controlled filenames. This can lead to remote code execution if executable files are uploaded to locations accessible via the web server.
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>= 5.0.0, <= 5.8.0.135>= 5.0.0, <= 5.8.0.135CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 installed Vocera productLocate Vocera Report Server or Voice Server installation directory and identify the specific product and version installed. Check common installation paths or use system inventory tools.Affected if The installed product is Vocera Report Server or Voice Server with version 5.0.0 through 5.8.0.135
-
Check installed version numberQuery the installed Vocera application for its exact version number. This is typically available in the application UI, an about dialog, or a version file within the installation directory.Affected if The version falls within >= 5.0.0 and <= 5.8.0.135 for either product
-
Verify upload endpoint exposureIdentify if the web interface multipart/form-data upload endpoint for the BaseController class is exposed and accessible. Check web server configuration for paths related to file uploads.Affected if The file upload endpoint is accessible without additional authentication or validation controls
-
Inspect upload-staging directoryLocate and examine the upload-staging directory for unexpected or unauthorized files. Look for executable file types (e.g., .jsp, .asp, .php, .exe, .sh) that were not intentionally uploaded through legitimate workflows.Affected if Arbitrary files with user-controlled names or executable extensions exist in the staging directory
-
Review web root for uploaded executablesCheck web-accessible directories for any recently created or unexpected executable files that may have been placed there through the unrestricted upload vulnerability.Affected if Executable files are present in web-accessible locations that were not intentionally deployed through legitimate application processes
You are affected if Vocera Report Server or Voice Server version 5.0.0 through 5.8.0.135 is installed AND the web-based file upload functionality is accessible, with potential indicator being unexpected files in staging or web directories.
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 filename validation, restrict allowed file extensions/types, add authentication requirements, and ensure uploaded files are not executable or stored outside the web root.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-46899 — 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-46899 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