CVE-2024-6922
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 · uneditedAutomation Anywhere Automation 360 v21-v32 is vulnerable to Server-Side Request Forgery in a web API component. An attacker with unauthenticated access to the Automation 360 Control Room HTTPS service (port 443) or HTTP service (port 80) can trigger arbitrary web requests from the server.
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 confidenceAutomation Anywhere Automation 360 versions v21 through v32 contains a Server-Side Request Forgery (SSRF) vulnerability in a web API component. An unauthenticated attacker with network access to the Control Room service (port 80 or 443) can cause the server to make arbitrary outbound HTTP requests to internal or external resources, potentially bypassing network segmentation and accessing internal services.
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
- Network
- Complexity
- Low
- Privileges
- None
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
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 Automation 360 versionAccess the Control Room administration interface and navigate to the About or Version section, or check the installation directory for version manifest files. Alternatively, query the Control Room API endpoint that returns version information if accessible.Affected if The installed version falls within v21 through v32 (inclusive).
-
Verify Control Room web service exposureDetermine if the Control Room service is listening on port 80 or 443 by running a network scan or checking the server configuration: 'netstat -an | grep -E ':(80|443)' or review the web server configuration files for the Control Room.Affected if Port 80 or 443 is open and accepting connections from untrusted networks.
-
Confirm API endpoint accessibilityAttempt to access the web API component endpoint without authentication using a tool like curl or a browser: 'curl -I <control-room-url>/api/<vulnerable-endpoint>' to check if the endpoint responds without requiring login credentials.Affected if The API endpoint responds to unauthenticated requests, indicating the vulnerable component is exposed.
-
Check network segmentation controlsReview firewall rules or network ACLs controlling outbound HTTP traffic from the Automation 360 server. Document any allowed external or internal destinations.Affected if The server has unrestricted outbound network access, allowing arbitrary HTTP requests to internal services or external resources.
A user is affected if their Automation 360 installation is version 21 through 32, the Control Room API is exposed on port 80/443 without authentication, and the server can make outbound HTTP requests to arbitrary destinations.
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 dataRestrict outbound network access from the Automation 360 server and implement URL allowlisting in the affected API component. Consider adding authentication requirements to the vulnerable endpoint if not already present.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6922 — 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-6922 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