Skip to content
Fencer Intel
high 7.5

CVE-2011-2900 in the critical feed json

Stack-based buffer overflow in the (1) put_dir function in mongoose.c in Mongoose 3.0, (2) put_dir function in yasslEWS.c in yaSSL Embedded…

published 2011-08-05 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-2873

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
13.3%
EPSS 13.3% chance of exploitation in 30 days, percentile 96%
public exploits
2
Exploit-DB

Summary

Stack-based buffer overflow in the (1) put_dir function in mongoose.c in Mongoose 3.0, (2) put_dir function in yasslEWS.c in yaSSL Embedded Web Server (yasslEWS) 0.2, and (3) _shttpd_put_dir function in io_dir.c in Simple HTTPD (shttpd) 1.42 allows remote attackers to execute arbitrary code via an HTTP PUT request, as exploited in the wild in 2011.

Patch / fix

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2011-2900 updated cvss 4.3

mongoose: stack-based buffer overflow flaw in put_dir()

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Published
  2. First public exploit (EDB-17658)

Exploit prediction

13.26% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • EDB-17669 Simple HTTPd 1.42 - 'PUT' Remote Buffer Overflow remote, 2011-08-15
  • EDB-17658 Simple HTTPd 1.42 - Denial of Servive dos, 2011-08-12

CVSS scores

assigned by version score vector
NVD 2.0 7.5 AV:N/AC:L/Au:N/C:P/I:P/A:P

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.