Skip to main content
Mallory
MediumPublic exploitVulnerability

CVE-2015-1548: Out-of-bounds read in mini_httpd long protocol string handling

Published Feb 10, 2015 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS5.0Medium · v2
EPSS1.6%76th percentile
CISA KEVNoNot listed
In the wildReported2 exploitation records in Mallory
Vendor
Acme
IdentifiersCVE-2015-1548CWE-125

CVE-2015-1548 is an information disclosure vulnerability in mini_httpd 1.21 and earlier. A remote attacker can send an HTTP request containing an excessively long protocol string, triggering an incorrect response size calculation that causes an out-of-bounds read from process memory. The flaw affects request parsing and response generation logic in mini_httpd, allowing memory beyond the intended buffer boundary to be included in the server response.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can disclose sensitive information from the memory space of the mini_httpd process. Depending on runtime state, exposed memory may include application data, credentials, session material, configuration fragments, or other sensitive process-resident information. The vulnerability is primarily an information leak rather than direct code execution, but disclosed memory could facilitate follow-on compromise.

Mitigation

If you can’t patch tonight, do this now.

If an update is not immediately available, restrict exposure of mini_httpd to trusted networks, place the service behind access controls or filtering, and minimize direct internet reachability. Monitor for malformed HTTP requests with unusually long protocol strings and consider compensating controls such as reverse proxies, network segmentation, and temporary service disablement on unnecessary interfaces.

Remediation

Patch, then assume compromise.

Upgrade mini_httpd to a fixed version newer than 1.21. Where mini_httpd is embedded in appliances or firmware, apply the vendor-provided firmware or software update that incorporates the patched component. Asset owners should identify devices and products that bundle vulnerable mini_httpd versions and prioritize patching internet-exposed systems.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
AcmeMini Httpdapplication
FAQ

Frequently asked questions

Is CVE-2015-1548 exploited in the wild?
Yes. As of Oct 16, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2015-1548?
Yes. As of Oct 16, 2026, Mallory has reports of a public exploit for CVE-2015-1548.
Is there a patch for CVE-2015-1548?
Upgrade mini_httpd to a fixed version newer than 1.21. Where mini_httpd is embedded in appliances or firmware, apply the vendor-provided firmware or software update that incorporates the patched component.
What products are affected by CVE-2015-1548?
Acme Mini Httpd.
How severe is CVE-2015-1548?
CVE-2015-1548 has a CVSS v2 score of 5.0 (Medium) and an EPSS score of 1.6% (76th percentile) as of Oct 16, 2026.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence1Every report linking this CVE to a named adversary.
Associated malware4Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.