CVE-2022-50796
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 · uneditedSOUND4 IMPACT/FIRST/PULSE/Eco <=2.x contains an unauthenticated remote code execution vulnerability in the firmware upload functionality with path traversal flaw. Attackers can exploit the upload.cgi script to write malicious files to the system with www-data permissions, enabling unauthorized access and code execution.
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 confidenceSOUND4 IMPACT/FIRST/PULSE/Eco devices (firmware <=2.x) contain an unauthenticated remote code execution vulnerability in the firmware upload functionality. The upload.cgi script has a path traversal flaw allowing attackers to write malicious files to arbitrary locations on the system with www-data (web server) permissions, enabling remote code execution.
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= 2.15= 1.69= 2.15= 1.69= 2.15= 1.69= 1.16= 1.16= 1.2= 1.30= 1.11CVSS 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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 the SOUND4 device modelAccess the device web interface or check the device label/documentation to confirm the exact model (Impact, Pulse, First, Impact Eco, Pulse Eco, Big Voice4, Big Voice2, or Wm2)Affected if The device is any of the listed affected models
-
Check the installed firmware versionLog into the device web interface and navigate to the system status or firmware information page to view the current firmware versionAffected if The firmware version matches 2.15, 1.69, 1.16, 1.2, 1.30, or 1.11 for the respective model
-
Verify upload.cgi is accessibleAttempt to access http://[device-ip]/cgi-bin/upload.cgi or https://[device-ip]/cgi-bin/upload.cgi from a remote locationAffected if The upload.cgi script responds (even with an error) indicating the endpoint exists and is reachable
-
Confirm web server is runningCheck if the device web interface is accessible on ports 80 or 443, or use a network scan to confirm the HTTP/HTTPS service is activeAffected if The web server is running and accepting connections on standard HTTP ports
The device is affected if it is a SOUND4 Impact, Pulse, First, Impact Eco, Pulse Eco, Big Voice4, Big Voice2, or Wm2 device running any of the listed firmware versions and the web interface (including upload.cgi) is network-accessible.
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 dataImmediately restrict network access to the upload.cgi endpoint, apply vendor firmware updates if available, and consider network segmentation to limit exposure of the affected device.
- 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-50796 — 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-50796 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