# CVE-2023-38843: Code injection in n/a

> An authenticated attacker can execute arbitrary code by injecting a crafted payload into the incident description field in Atlos.

- **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Aug 2023
- **Updated:** 8 Oct 2024
- **Also known as:** GHSA-5hvw-cmc2-mpjr

## What is CVE-2023-38843?

CVE-2023-38843 is a high-severity code injection vulnerability in n/a, published on 17 Aug 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

An issue in Atlos v.1.0 allows an authenticated attacker to execute arbitrary code via a crafted payload into the description field in the incident function.

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

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

It affects 1 product.


Products: Atlos Atlos.

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

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

## Is CVE-2023-38843 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38843 is a high-severity code injection vulnerability in n/a, published on 17 Aug 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-38843 exists.

Affected product: n/a. 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-38843/ (Markdown: https://insights.sbomify.com/CVE-2023-38843/index.md)
```

## Sources

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

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