CVE-2010-1185 in the critical feed json
Stack-based buffer overflow in serv.exe in SAP MaxDB 7.4.3.32, and 7.6.0.37 through 7.6.06 allows remote attackers to execute arbitrary cod…
published 16y ago modified 4mo ago also EUVD-2010-1215
- cvss
- 10.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 15.2%
- EPSS 15.2% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
Stack-based buffer overflow in serv.exe in SAP MaxDB 7.4.3.32, and 7.6.0.37 through 7.6.06 allows remote attackers to execute arbitrary code via an invalid length parameter in a handshake packet to TCP port 7210. NOTE: some of these details are obtained from third party information.
Is CVE-2010-1185 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-11886)
- Published
Exploit prediction
15.22% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-11886 SAP MaxDB - Malformed Handshake Request Remote Code Execution remote, 2010-03-26
- securityfocus.com http://www.securityfocus.com/bid/38769 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
-
securityfocus.com
/bid/38769
vdb-entry, exploit
-
vupen.com
/english/advisories/2010/0643
vdb-entry, vendor-advisory
-
secunia.com
/advisories/38955
third-party-advisory, vendor-advisory
-
osvdb.org
/63047
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/56950
vdb-entry
-
securitytracker.com
/id?1023719
vdb-entry
- zerodayinitiative.com /advisories/ZDI-10-032/
-
securityfocus.com
/archive/1/510125/100/0/threaded
mailing-list
Sources
- CVE List CVE-2010-1185
- NVD CVE-2010-1185
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.