# CVE-2007-2053: Memory corruption in n/a

> Remote attackers can cause denial of service or execute arbitrary code via stack-based buffer overflows in AFFLIB library functions.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Apr 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-p766-86xm-7h4p

## What is CVE-2007-2053?

CVE-2007-2053 is a critical memory corruption vulnerability in n/a, published on 30 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple stack-based buffer overflows in AFFLIB before 2.2.6 allow remote attackers to cause a denial of service (crash) or possibly execute arbitrary code via (1) a long LastModified value in an S3 XML response in lib/s3.cpp; (2) a long (a) path or (b) bucket in an S3 URL in lib/vnode_s3.cpp; or (3) a long (c) EFW, (d) AFD, or (c) aimage file path.  NOTE: the aimage vector (3c) has since been recalled from the researcher's original advisory, since the code is not called in any version of AFFLIB.

## Which versions are affected by CVE-2007-2053?

It affects 1 product.


Products: Afflib Afflib.

## How do I fix CVE-2007-2053?

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

## Is CVE-2007-2053 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2007-2352](https://insights.sbomify.com/CVE-2007-2352/): Other in n/a (critical 10.0)
- [CVE-2007-2054](https://insights.sbomify.com/CVE-2007-2054/): Memory corruption in n/a (high 7.5)
- [CVE-2007-2055](https://insights.sbomify.com/CVE-2007-2055/): Command injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-2053 and fix it if it is affected.

What it is: CVE-2007-2053 is a critical memory corruption vulnerability in n/a, published on 30 Apr 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2007-2053 in the wild and no public exploit code.

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-2007-2053/ (Markdown: https://insights.sbomify.com/CVE-2007-2053/index.md)
```

## Sources

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

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