CVE-2003-1051 json
Multiple format string vulnerabilities in IBM DB2 Universal Database 8.1 may allow local users to execute arbitrary code via certain comman…
published 22y ago modified 4mo ago also EUVD-2003-1041
- cvss
- 7.2
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 3
- Exploit-DB
Summary
Multiple format string vulnerabilities in IBM DB2 Universal Database 8.1 may allow local users to execute arbitrary code via certain command line arguments to (1) db2start, (2) db2stop, or (3) db2govd.
Patch / fix
- securityfocus.com/bid/8989 advisory
Is CVE-2003-1051 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-23346)
- Published
Exploit prediction
1.26% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-14).
Exploits and checks
- EDB-23346 IBM DB2 - 'db2govd' Format String Arbitrary Code Execution local, 2003-11-07
- EDB-23345 IBM DB2 - 'db2stop' Format String Arbitrary Code Execution local, 2003-11-07
- EDB-23344 IBM DB2 - 'db2start' Format String Arbitrary Code Execution local, 2003-11-07
- securityfocus.com http://www.securityfocus.com/bid/8989 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.2 | AV:L/AC:L/Au:N/C:C/I:C/A:C |
Classification
- Technology feeds
References
-
securityfocus.com
/bid/8989
vdb-entry, exploit, patch, vendor-advisory
-
securityfocus.com
/archive/1/343804
mailing-list, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/13633
vdb-entry
- secnetops.com /research/advisories/SRT2003-11-06-0710.txt
Sources
- CVE List CVE-2003-1051
- NVD CVE-2003-1051
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.