# CVE-2023-37275: System logs spoofable in Auto-GPT via ANSI control sequences

> Attackers can spoof system logs in Auto-GPT using ANSI escape sequences, potentially misleading users into executing malicious commands.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Jul 2023
- **Updated:** 22 Oct 2024
- **Also known as:** GHSA-r7f7-qrrv-3fjh

## What is CVE-2023-37275?

CVE-2023-37275 is a low-severity vulnerability in Significant-Gravitas Auto-GPT, published on 13 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Auto-GPT is an experimental open-source application showcasing the capabilities of the GPT-4 language model. The Auto-GPT command line UI makes heavy use of color-coded print statements to signify different types of system messages to the user, including messages that are crucial for the user to review and control which commands should be executed. Before v0.4.3, it was possible for a malicious external resource (such as a website browsed by Auto-GPT) to cause misleading messages to be printed to the console by getting the LLM to regurgitate JSON encoded ANSI escape sequences (`\u001b[`). These escape sequences were JSON decoded and printed to the console as part of the model's "thinking process". The issue has been patched in release version 0.4.3.

Weakness: CWE-117 (Improper Output Neutralization for Logs)

## Which versions are affected by CVE-2023-37275?

It affects 1 product.


Products: Agpt Autogpt Classic.

## How do I fix CVE-2023-37275?

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

## Is CVE-2023-37275 being exploited?

There is no known exploitation of CVE-2023-37275 in the wild and no public exploit code.

## Other vulnerabilities in Significant-Gravitas Auto-GPT

- [CVE-2024-6091](https://insights.sbomify.com/CVE-2024-6091/): Shell Command Denylist Bypass in significant-gravitas/autogpt (critical 9.8)
- [CVE-2024-8156](https://insights.sbomify.com/CVE-2024-8156/): Command Injection in significant-gravitas/autogpt (high 8.8)
- [CVE-2024-1879](https://insights.sbomify.com/CVE-2024-1879/): CSRF to RCE in significant-gravitas/autogpt (high 8.8)
- [CVE-2024-1881](https://insights.sbomify.com/CVE-2024-1881/): Improper Neutralization of Special Elements used in an OS Command in significant-gravitas/autogpt (high 8.8)
- [CVE-2023-37273](https://insights.sbomify.com/CVE-2023-37273/): Docker escape in Auto-GPT when running from docker-compose.yml included in git repo (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-37275 and fix it if it is affected.

What it is: CVE-2023-37275 is a low-severity vulnerability in Significant-Gravitas Auto-GPT, published on 13 Jul 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-37275 in the wild and no public exploit code.

Affected product: Significant-Gravitas Auto-GPT. 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-2023-37275/ (Markdown: https://insights.sbomify.com/CVE-2023-37275/index.md)
```

## Sources

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

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