CVE-2024-47856
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 · uneditedIn RSA Authentication Agent before 7.4.7, service paths and shortcut paths may be vulnerable to path interception if the path has one or more spaces and is not surrounded by quotation marks. An adversary can place an executable in a higher-level directory of the path, and Windows will resolve that executable instead of the intended executable.
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 · high confidenceRSA Authentication Agent before version 7.4.7 contains a path interception vulnerability in service and shortcut paths. When paths contain one or more spaces and are not surrounded by quotation marks, Windows may resolve an attacker-controlled executable in a higher-level directory instead of the intended executable, leading to arbitrary code execution.
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< 7.4.7CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 installed RSA Authentication Agent versionOpen Programs and Features (appwiz.cpl) or run 'Get-WmiObject -Class Win32_Product | Where-Object {$_.Name -like "*RSA*"}' to list installed RSA components, or check the version property of the main executable (typically named SecurID.dll or RSAAGTSvc.exe) in the installation directoryAffected if The displayed version is lower than 7.4.7 (e.g., 7.4.6, 7.4.5, etc.)
-
Check Windows service executable pathsRun 'sc qc RSAAGTSvc' (or the actual service name found in services.msc for RSA Authentication Agent) to query the service configuration, then examine the BINARY_PATH_NAME fieldAffected if The BINARY_PATH_NAME contains spaces and is NOT enclosed in quotation marks (e.g., C:\Program Files\RSA\Agent\bin\RSAAGTSvc.exe instead of "C:\Program Files\RSA\Agent\bin\RSAAGTSvc.exe")
-
Inspect service path for directory traversal potentialIn the service's BINARY_PATH_NAME (if unquoted), identify any directory paths with spaces (e.g., 'Program Files' or 'RSA Security'), then verify whether a malicious executable with the same base name exists in any parent or sibling directory that Windows could resolve firstAffected if The path has unquoted spaces and a similarly-named executable exists in a higher-level directory that Windows might load before the intended one
-
Review RSA Authentication Agent shortcutsLocate shortcuts ( .lnk files) for RSA Authentication Agent in the Start Menu or Desktop, then right-click each shortcut, select Properties, and examine the Target fieldAffected if The Target path contains spaces and is NOT enclosed in quotation marks, creating a similar path interception risk as with services
You are affected if RSA Authentication Agent for Windows is installed at a version lower than 7.4.7 AND any service or shortcut path containing spaces is not enclosed in quotation marks.
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.
dbcve · scoped7.4.7
Upgrade to RSA Authentication Agent 7.4.7 or later, and audit all service and shortcut configurations to ensure paths with spaces are properly quoted.
7.4.7
- Identify the current version of RSA Authentication Agent for Windows by checking Add/Remove Programs or the program's About section
- Download RSA Authentication Agent for Windows version 7.4.7 or later from the official RSA community or support portal
- Schedule a maintenance window for the upgrade process
- Backup the current configuration and any relevant system state
- Run the installer for version 7.4.7 with appropriate administrator privileges
- Follow the on-screen installation prompts to complete the upgrade
- Restart the RSA Authentication Agent service if not done automatically by the installer
- Verify the installed version is 7.4.7 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47856 — 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-47856 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