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

> Unauthenticated attackers can trigger arbitrary server-side requests via the Control Room API, potentially accessing internal resources.

- **Severity:** Medium 6.9 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Jul 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-wwxv-fvxx-vp4c

## What is CVE-2024-6922?

CVE-2024-6922 is a medium-severity server-side request forgery vulnerability in Automationanywhere Automation 360, published on 26 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-6922?


## How do I fix CVE-2024-6922?

No fix has been published for CVE-2024-6922 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-6922 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6922 exists.

Public exploit code:

- Automation Anywhere Automation 360 - Server-Side Request Forgery (nuclei): http/cves/2024/CVE-2024-6922.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6922 and fix it if it is affected.

What it is: CVE-2024-6922 is a medium-severity server-side request forgery vulnerability in Automationanywhere Automation 360, published on 26 Jul 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-6922 exists.

Affected product: Automationanywhere Automation 360. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-6922/ (Markdown: https://insights.sbomify.com/CVE-2024-6922/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-6922
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-6922
- OSV: https://osv.dev/vulnerability/CVE-2024-6922

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-6922/
Summaries are generated and may contain mistakes; the official description above is the record.