CVE-2024-47560
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 · uneditedRevoWorks Cloud Client 3.0.91 and earlier contains an incorrect authorization vulnerability. If this vulnerability is exploited, unintended processes may be executed in the sandbox environment. Even if malware is executed in the sandbox environment, it does not compromise the client's local environment. However, information in the sandbox environment may be disclosed to outside or behaviors of the sandbox environment may be violated by tampering registry.
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 confidenceRevoWorks Cloud Client 3.0.91 and earlier contains an incorrect authorization vulnerability that allows unintended processes to execute within the sandbox environment. While the sandbox isolates the local client from direct compromise, the flaw enables information disclosure from the sandboxed environment and allows tampering with sandbox behavior via registry modifications.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 RevoWorks Cloud Client installationLocate the RevoWorks Cloud Client installation directory (typically under Program Files or Program Files x86) and check the executable version property, or use system inventory tools that list installed softwareAffected if The software is installed and version is 3.0.91 or earlier
-
Compare installed version to affected rangeObtain the exact version number from the installed software and compare against 3.0.91 - versions 3.0.91 and earlier are within the affected rangeAffected if Installed version is 3.0.91 or any earlier version number
-
Determine if sandbox functionality is in useReview whether the RevoWorks Cloud Client sandbox feature is actively used or configured in the environment - check for any sandbox-related configurations, sessions, or active virtualized instancesAffected if The sandbox feature is actively used or configured, as the vulnerability only affects sandboxed process execution
-
Inspect sandbox-related registry keys for unauthorized changesExamine registry locations where RevoWorks Cloud Client stores sandbox configuration settings (typically under HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER in software-specific paths) for any unexpected modifications or unauthorized entriesAffected if Registry keys show modifications that were not initiated by legitimate administrators or the software's normal operation
A system is affected if RevoWorks Cloud Client version 3.0.91 or earlier is installed and the sandbox feature is being used, with registry changes indicating potential exploitation of the authorization flaw.
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 dataUpdate to a version beyond 3.0.91 that includes proper authorization checks before process execution within the sandbox environment. If no update is available, restrict user privileges and monitor sandbox registry keys for unauthorized changes.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47560 — 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-2024-47560 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