# CVE-2024-22857: Memory corruption in n/a

> A heap-based buffer overflow in the zlog library allows attackers to achieve arbitrary code execution by overwriting function pointers.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 7 Mar 2024
- **Updated:** 27 Aug 2024
- **Also known as:** GHSA-6q5p-rp5c-wmph, OESA-2024-2213, OESA-2024-2214, OESA-2024-2215, OESA-2024-2318

## What is CVE-2024-22857?

CVE-2024-22857 is a critical memory corruption vulnerability in n/a, published on 7 Mar 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Heap based buffer flow in zlog v1.1.0 to v1.2.17 in zlog_rule_new().The size of record_name is MAXLEN_PATH(1024) + 1 but file_path may have data upto MAXLEN_CFG_LINE(MAXLEN_PATH*4) + 1. So a check was missing in zlog_rule_new() while copying the record_name from file_path + 1 which caused the buffer overflow. An attacker can exploit this vulnerability to overwrite the zlog_record_fn record_func function pointer to get arbitrary code execution or potentially cause remote code execution (RCE).

Weakness: CWE-122 (Heap-based Buffer Overflow)

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


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

Apply the vendor's patch.

## Is CVE-2024-22857 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22857 is a critical memory corruption vulnerability in n/a, published on 7 Mar 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-22857 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-2024-22857/ (Markdown: https://insights.sbomify.com/CVE-2024-22857/index.md)
```

## Sources

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

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