# CVE-2015-1548: Information disclosure in n/a

> Remote attackers can read sensitive process memory via a crafted HTTP request, potentially exposing confidential data.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Feb 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2015-1548, GHSA-p64m-82xx-9xm7

## What is CVE-2015-1548?

CVE-2015-1548 is a medium-severity vulnerability in n/a, published on 10 Feb 2015. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mini_httpd 1.21 and earlier allows remote attackers to obtain sensitive information from process memory via an HTTP request with a long protocol string, which triggers an incorrect response size calculation and an out-of-bounds read.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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

It affects 1 product.


Products: Acme Mini Httpd.

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

Upgrade to a fixed version.

## Is CVE-2015-1548 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-17663](https://insights.sbomify.com/CVE-2017-17663/): Memory corruption in n/a (critical 9.8)
- [CVE-2009-4490](https://insights.sbomify.com/CVE-2009-4490/): Command injection in n/a (medium 5.0)
- [CVE-2001-0893](https://insights.sbomify.com/CVE-2001-0893/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-1548 is a medium-severity vulnerability in n/a, published on 10 Feb 2015. 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-2015-1548 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-2015-1548/ (Markdown: https://insights.sbomify.com/CVE-2015-1548/index.md)
```

## Sources

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

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