CVE-2022-50696
Hardcoded credentials in SOUND4 devices allow unauthorized access.
Is CVE-2022-50696 being exploited?
Not confirmed. CVE-2022-50696 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.58% probability of exploitation in the next 30 days.
How severe is CVE-2022-50696?
CVE-2022-50696 is rated Critical with a CVSS score of 9.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2022-50696?
Not known from our data. No patch reference has been recorded for CVE-2022-50696, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2022-50696 affect?
CVE-2022-50696 affects SOUND4 IMPACT 2.x and below, SOUND4 FIRST 2.x and below, SOUND4 PULSE 2.x and below, SOUND4 Eco 2.x and below. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2022-50696?
Firmware upgrade when patched; apply network isolation.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthorized access via static credentials; no user interaction; cross-OS (Linux/Windows).
Monitor only
- affected1.30
- affected1.2
- affected1.16
- affectedVersion 2: 1.1/2.15
- affected1.1/2.4.29
- affected1.11
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.