dbcve.org
Copy9Application · 1byte

CVE-2022-0732

HIGH · 7.5 CVSS v3.1 Published 2022-02-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 · moderate confidence

The backend infrastructure shared by multiple mobile device monitoring services lacks proper authentication and authorization validation on API endpoints, creating an IDOR vulnerability where attackers can access or modify monitoring data belonging to other users by manipulating object references in requests.

MitigationImplement robust authentication mechanisms and enforce proper authorization checks on all API endpoints to validate user permissions before granting access to monitoring data resources.

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
Copy9Application
Affected:all versions
ExactspyApplication
Affected:all versions
FonetrackerApplication
Affected:all versions
GuestspyApplication
Affected:all versions
IspyooApplication
Affected:all versions
MxspyApplication
Affected:all versions
SecondcloneApplication
Affected:all versions
The Truth SpyApplication
Affected:all versions

CVSS 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify if a 1byte monitoring product is deployed
    Search your environment for installations or processes related to: Copy9, Exactspy, Fonetracker, Guestspy, Ispyoo, Mxspy, Secondclone, or The Truth Spy. Check installed applications, running services, or hosted web applications for these product names.
    Affected if Any of these eight monitoring products are present in the environment
  2. Locate the shared backend API infrastructure
    Search for web services or APIs hosted on infrastructure labeled as '1byte' or check web application source code for references to 1byte backend services.
    Affected if The backend infrastructure is labeled as or references '1byte'
  3. Verify API endpoint accessibility
    If 1byte backend services are found, test API endpoints by sending requests without authentication headers or session tokens to monitor user data endpoints.
    Affected if API endpoints respond without requiring valid authentication credentials
  4. Check for IDOR vulnerability in object references
    Attempt to access or modify monitoring data by manipulating object IDs, user IDs, or resource identifiers in API requests (e.g., change a monitored user ID to a different user's ID).
    Affected if Requests with manipulated object references successfully return or modify data belonging to other users
  5. Review API authorization logic
    Examine API endpoint code or configuration to confirm whether authorization checks validate user permissions before returning monitoring data resources.
    Affected if The API lacks proper authorization validation logic before serving monitoring data

If any of the eight 1byte monitoring products are deployed and the backend API is accessible without authentication or allows object reference manipulation, the environment is affected by CVE-2022-0732.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement robust authentication mechanisms and enforce proper authorization checks on all API endpoints to validate user permissions before granting access to monitoring data resources.

Recommended fix High confidence
  1. These are surveillance/spyware applications with a backend IDOR vulnerability. No user-actionable fix is available.
  2. Discontinue use of the affected applications (Copy9, Exactspy, Fonetracker, Guestspy, Ispyoo, Mxspy, Secondclone, The Truth Spy) as the vulnerability is in the vendor's backend infrastructure.
  3. The vulnerability requires the vendors to remediate their backend API access controls - end users cannot patch or configure a fix.
  4. Consider using reputable, actively maintained mobile device management or security tools from trusted vendors if monitoring functionality is required.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Copy9 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-0732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-0732 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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