CVE-2009-4873 in the critical feed json
Stack-based buffer overflow in the HTTP server in Rhino Software Serv-U Web Client 9.0.0.5 allows remote attackers to cause a denial of ser…
published 16y ago modified 4mo ago also EUVD-2009-4836
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 20.6%
- EPSS 20.6% chance of exploitation in 30 days, percentile 97%
- public exploits
- 2
- Exploit-DB
Summary
Stack-based buffer overflow in the HTTP server in Rhino Software Serv-U Web Client 9.0.0.5 allows remote attackers to cause a denial of service (server crash) or execute arbitrary code via a long Session cookie.
Is CVE-2009-4873 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-9966)
- Published
Exploit prediction
20.55% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-9966 Serv-U Web Client 9.0.0.5 - Remote Buffer Overflow (1) remote, 2009-11-02
- EDB-9800 Serv-U Web Client 9.0.0.5 - Remote Buffer Overflow (2) remote, 2009-11-05
- rangos.de http://www.rangos.de/ServU-ADV.txt referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/36895 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 10.0 | AV:N/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
References
-
rangos.de
/ServU-ADV.txt
exploit
-
securityfocus.com
/bid/36895
vdb-entry, exploit
-
vupen.com
/english/advisories/2009/3116
vdb-entry, vendor-advisory
-
secunia.com
/advisories/37228
third-party-advisory, vendor-advisory
Sources
- CVE List CVE-2009-4873
- NVD CVE-2009-4873
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.