Copy9: Authorization Bypass Through User-Controlled Key
CVE-2022-0732 is a high-severity authorization bypass through user-controlled key vulnerability in Copy9 from 1Byte, 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 Copy9 versions: All. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 2.51% chance of exploitation within 30 days, higher than 85% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of Copy9 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 |
|---|---|---|---|
| 1Byte | Copy9 | All | Not stated |
| 1Byte | FoneTracker | All | Not stated |
| 1Byte | iSpyoo | All | Not stated |
| 1Byte | GuestSpy | All | Not stated |
| 1Byte | TheSpyApp | All | Not stated |
| 1Byte | ExactSpy | All | Not stated |
| 1Byte | SecondClone | All | Not stated |
| 1Byte | The Truth Spy | All | Not stated |
| 1Byte | MxSpy | All | 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 3.1 | 7.5 | High | NVD |
| CVSS 2.0 | 5.0 | Medium | NVD |
Official description
The backend infrastructure shared by multiple mobile device monitoring services does not adequately authenticate or authorize API requests, creating an IDOR (Insecure Direct Object Reference) vulnerability.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Authorization Bypass Through User-Controlled Key
The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.
How developers prevent this class of flaw
- For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
- Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
- Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
More Authorization Bypass Through User-Controlled Key vulnerabilities (CWE-639)
Timeline
- CVE record published.
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- kb.cert.org/vuls/id/229438Third Party Advisory, US Government Resource
- techcrunch.com/2022/02/22/stalkerware-network-spilling-data/Press/Media Coverage, Third Party Advisory
- kb.cert.org/vuls/id/229438Third Party Advisory, US Government Resource
Other references
- cwe.mitre.org/data/definitions/284.htmlNot Applicable
Recent Authorization Bypass Through User-Controlled Key vulnerabilities
- 7.5 High severity
Spotted an error? Tell us.