# CVE-2015-10088: ayttm proxy.c http_connect format string

> A format string vulnerability in ayttm's proxy library allows remote attackers to potentially execute code or cause denial of service.

- **Severity:** Medium 5.0 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Mar 2023
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7v2r-ppmv-v8g5, UBUNTU-CVE-2015-10088

## What is CVE-2015-10088?

CVE-2015-10088 is a medium-severity vulnerability in ayttm, published on 5 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in ayttm up to 0.5.0.89. This affects the function http_connect in the library libproxy/proxy.c. The manipulation leads to format string. It is possible to initiate the attack remotely. The complexity of an attack is rather high. The exploitability is told to be difficult. The patch is named 40e04680018614a7d2b68566b261b061a0597046. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-222267.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

## Which versions are affected by CVE-2015-10088?

It affects 1 product.


Products: Ayttm Project Ayttm.

## How do I fix CVE-2015-10088?

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

## Is CVE-2015-10088 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-10088 and fix it if it is affected.

What it is: CVE-2015-10088 is a medium-severity vulnerability in ayttm, published on 5 Mar 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-10088 in the wild and no public exploit code.

Affected product: ayttm. 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-2015-10088/ (Markdown: https://insights.sbomify.com/CVE-2015-10088/index.md)
```

## Sources

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

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