Impact/Pulse/First: Improper Limitation of a Pathname to a Restricted Directory
CVE-2022-50792 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in Impact/Pulse/First from Sound4, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected Impact/Pulse/First versions: Version 2: 1.1/2.15. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 1.57% chance of exploitation within 30 days, higher than 76% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Impact/Pulse/First you run against the affected versions below, and install the vendor's latest release.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| SOUND4 | Impact/Pulse/First | Version 2: 1.1/2.15 | Not stated |
| SOUND4 | Impact/Pulse Eco | 1.16 | Not stated |
| SOUND4 | BigVoice4 | 1.2 | Not stated |
| SOUND4 | BigVoice2 | 1.30 | Not stated |
| SOUND4 | Stream | 1.1/2.4.29 | Not stated |
| Kantar Media | WM2 | 1.11 | Not stated |
| Sound4 | Impact Firmware | 2.15; 1.69 | Not stated |
| Sound4 | Pulse Firmware | 2.15; 1.69 | Not stated |
| Sound4 | First Firmware | 2.15; 1.69 | Not stated |
| Sound4 | Impact Eco Firmware | 1.16 | Not stated |
| Sound4 | Pulse Eco Firmware | 1.16 | Not stated |
| Sound4 | Big Voice4 Firmware | 1.2 | Not stated |
| Sound4 | Big Voice2 Firmware | 1.30 | Not stated |
| Sound4 | Wm2 Firmware | 1.11 | Not stated |
| Sound4 | Stream Extension | 2.4.29 | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- NoneNothing can be modified.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 8.7 | High | CNA (vulncheck.com) |
| CVSS 3.1 | 7.5 | High | CNA (vulncheck.com) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
SOUND4 IMPACT/FIRST/PULSE/Eco versions 2.x and below contain an unauthenticated file disclosure vulnerability that allows remote attackers to access sensitive system files. Attackers can exploit the vulnerability by manipulating the 'file' GET parameter to disclose arbitrary files on the affected device.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
- Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.
More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- exchange.xforce.ibmcloud.com/vulnerabilities/247916Third Party Advisory
- vulncheck.com/advisories/sound-impactfirstpulseeco-x-unauthenticated-file-disclosure-vulnerabilityThird Party Advisory
Technical write-ups (may include proof of concept)
- packetstormsecurity.com/files/170263/SOUND4-IMPACT-FIRST-PULSE-Eco-2.x-Unauthenticated-File-Disclosure.htmlExploit, Third Party Advisory, VDB Entry
- zeroscience.mk/en/vulnerabilities/ZSL-2022-5736.phpExploit, Third Party Advisory
Other references
- sound4.com/Product
Other vulnerabilities in Impact/Pulse/First
- 9.8 Critical severity
- 7.8 High severity
- 9.8 Critical severity
- 8.8 High severity
- 7.8 High severity
- 7.5 High severity
Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities
- 7.5 High severity
- 7.5 High severity
- 7.2 High severity
- 7.3 High severity
- 7.8 High severity
- 7.8 High severity
Spotted an error? Tell us.