CVE-2009-0689: Array index error in the (1) dtoa implementation in dtoa.c (aka pdtoa.c) and the (2) gdtoa (aka new dtoa) implementation in gdtoa/misc.c in…
Noroxi assessment
Priority: Monitor (action score 36/100)
- Public proof-of-concept code exists (Exploit-DB, GitHub); there is no record of exploitation in the wild.
- Probability of exploitation in the next 30 days: 29.3% (FIRST EPSS); higher than 98.2% of all records.
- Fixed version: mono (Debian:12) 4.2.1.102+dfsg2-4; nspr (Debian:12) 4.8-2; kdelibs (Debian:5.0) 4:3.5.10.dfsg.1-0lenny4.
Low priority for now. Upgrade to mono (Debian:12) 4.2.1.102+dfsg2-4; nspr (Debian:12) 4.8-2; kdelibs (Debian:5.0) 4:3.5.10.dfsg.1-0lenny4 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Array index error in the (1) dtoa implementation in dtoa.c (aka pdtoa.c) and the (2) gdtoa (aka new dtoa) implementation in gdtoa/misc.c in libc, as used in multiple operating systems and products including in FreeBSD 6.4 and 7.2, NetBSD 5.0, OpenBSD 4.5, Mozilla Firefox 3.0.x before 3.0.15 and 3.5.x before 3.5.4, K-Meleon 1.5.3, SeaMonkey 1.1.8, and other products, allows context-dependent attackers to cause a denial of service (application crash) and possibly execute arbitrary code via a large precision value in the format argument to a printf function, which triggers incorrect memory allocation and a heap-based buffer overflow during conversion to a floating-point number.
- Published
- Jul 1, 2009
- Updated
- Jun 16, 2026
- EPSS
- 29.3% · 98th percentile
- CWE
- CWE-119
Report tools
Action score
36
Low priority for now.
- CVSS
- 27 / 40 · 6.8 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 9 / 30 · 29.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- Proof of concept exists, no weaponized module
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| k-meleon project | k-meleon | cpe:2.3:a:k-meleon_project:k-meleon |
| mozilla | firefox | cpe:2.3:a:mozilla:firefox |
| mozilla | seamonkey | cpe:2.3:a:mozilla:seamonkey |
| freebsd | freebsd | cpe:2.3:o:freebsd:freebsd |
| netbsd | netbsd | cpe:2.3:o:netbsd:netbsd |
| openbsd | openbsd | cpe:2.3:o:openbsd:openbsd |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- freebsd freebsd6.4
- freebsd freebsd7.2
- k-meleon project k-meleon1.5.3
- mozilla firefox3.0.1
- mozilla firefox3.0.10
- mozilla firefox3.0.11
- mozilla firefox3.0.12
- mozilla firefox3.0.13
+12 more rows
- mozilla firefox3.0.14
- mozilla firefox3.0.2
- mozilla firefox3.0.3
- mozilla firefox3.0.4
- mozilla firefox3.0.5
- mozilla firefox3.0.6
- mozilla firefox3.0.7
- mozilla firefox3.0.8
- mozilla firefox3.0.9
- mozilla firefox3.5
- mozilla firefox3.5.1
- mozilla firefox3.5.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | mono | before 4.2.1.102+dfsg2-4 | 4.2.1.102+dfsg2-4 |
| Debian:12 | nspr | before 4.8-2 | 4.8-2 |
| Debian:5.0 | kdelibs | before 4:3.5.10.dfsg.1-0lenny4 | 4:3.5.10.dfsg.1-0lenny4 |
| Debian:5.0 | nspr | before 4.7.1-5 | 4.7.1-5 |
| Debian:6.0 | mono | before 2.6.7-5.1+deb6u2 | 2.6.7-5.1+deb6u2 |
| Debian:8 | mono | before 3.2.8+dfsg-10+deb8u1 | 3.2.8+dfsg-10+deb8u1 |
| Red Hat:enterprise_linux:3::as | seamonkey | before 0:1.0.9-0.47.el3 | 0:1.0.9-0.47.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-chat | before 0:1.0.9-0.47.el3 | 0:1.0.9-0.47.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-debuginfo | before 0:1.0.9-0.47.el3 | 0:1.0.9-0.47.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-devel | before 0:1.0.9-0.47.el3 | 0:1.0.9-0.47.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-dom-inspector | before 0:1.0.9-0.47.el3 | 0:1.0.9-0.47.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-js-debugger | before 0:1.0.9-0.47.el3 | 0:1.0.9-0.47.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-mail | before 0:1.0.9-0.47.el3 | 0:1.0.9-0.47.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-nspr | before 0:1.0.9-0.47.el3 | 0:1.0.9-0.47.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-nspr-devel | before 0:1.0.9-0.47.el3 | 0:1.0.9-0.47.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-nss | before 0:1.0.9-0.47.el3 | 0:1.0.9-0.47.el3 |
| Red Hat:enterprise_linux:3::as | seamonkey-nss-devel | before 0:1.0.9-0.47.el3 | 0:1.0.9-0.47.el3 |
| Red Hat:enterprise_linux:4::as | firefox | before 0:3.0.15-3.el4 | 0:3.0.15-3.el4 |
| Red Hat:enterprise_linux:4::as | firefox-debuginfo | before 0:3.0.15-3.el4 | 0:3.0.15-3.el4 |
| Red Hat:enterprise_linux:4::as | kdelibs | before 6:3.3.1-17.el4_8.1 | 6:3.3.1-17.el4_8.1 |
| Red Hat:enterprise_linux:4::as | kdelibs-debuginfo | before 6:3.3.1-17.el4_8.1 | 6:3.3.1-17.el4_8.1 |
| Red Hat:enterprise_linux:4::as | kdelibs-devel | before 6:3.3.1-17.el4_8.1 | 6:3.3.1-17.el4_8.1 |
| Red Hat:enterprise_linux:4::as | nspr | before 0:4.7.6-1.el4_8 | 0:4.7.6-1.el4_8 |
| Red Hat:enterprise_linux:4::as | nspr-debuginfo | before 0:4.7.6-1.el4_8 | 0:4.7.6-1.el4_8 |
+96
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:kdelibs | 4:3.5.10.dfsg.1-0lenny4 · Debian:5.0 | Package registry (OSV) |
| debian:mono | 4.2.1.102+dfsg2-4 · Debian:12 | Package registry (OSV) |
| debian:nspr | 4.8-2 · Debian:12 | Package registry (OSV) |
| red hat:firefox | 0:3.0.15-3.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:firefox-debuginfo | 0:3.0.15-3.el4 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:nspr | 0:4.7.6-1.el4_8 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:nspr-debuginfo | 0:4.7.6-1.el4_8 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:nspr-devel | 0:4.7.6-1.el4_8 · Red Hat:enterprise_linux:4::as | Package registry (OSV) |
| red hat:seamonkey | 0:1.0.9-0.47.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-chat | 0:1.0.9-0.47.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:seamonkey-debuginfo | 0:1.0.9-0.47.el3 · Red Hat:enterprise_linux:3::as | Package registry (OSV) |
| red hat:xulrunner | 0:1.9.0.15-3.el5_4 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:xulrunner-debuginfo | 0:1.9.0.15-3.el5_4 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:xulrunner-devel | 0:1.9.0.15-3.el5_4 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:xulrunner-devel-unstable | 0:1.9.0.15-3.el5_4 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| suse:mono-core | 2.6.7-0.16.1 · SUSE:Linux Enterprise Software Development Kit 11 SP3 | Package registry (OSV) |
Exploit status
Proof of concept available
A public proof of concept or detection signature exists. Exploit knowledge is out there; don't delay patching.
Evidence
- Exploit-DB entry ×11
- Proof-of-concept repository on GitHub ×1
Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.
| Source | Kind | Date |
|---|---|---|
| Exploit-DB entry | dos | 2009-11-19 |
| Exploit-DB entry | dos | 2009-11-19 |
| Exploit-DB entry | dos | 2009-11-19 |
| Exploit-DB entry | dos | 2009-11-19 |
| Exploit-DB entry | dos | 2010-01-08 |
| Exploit-DB entry | dos | 2009-10-27 |
| Exploit-DB entry | remote | 2009-11-20 |
| Exploit-DB entry | dos | 2009-05-26 |
| Exploit-DB entry | remote | 2009-11-20 |
| Exploit-DB entry | dos | 2010-01-08 |
| Exploit-DB entry | remote | 2009-12-11 |
| Proof-of-concept repository on GitHub | stars:89 | 2018-12-18 |
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- First PoC-36 d
- Published
- TodayNov 16, 2026+6347 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
If successful
- Confidentiality
- P · data can be read
- Integrity
- P · data or configuration can be modified
- Availability
- P · the service can be disrupted
- Attack complexity
- M
- Confidentiality impact
- P
- Integrity impact
- P
- Availability impact
- P
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:N/AC:M/Au:N/C:P/I:P/A:P
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (19 more)Show less
- lists.apple.com/archives/security-announce/2010//Mar/msg00001.html
- lists.apple.com/archives/security-announce/2010/Jun/msg00003.html
- lists.opensuse.org/opensuse-security-announce/2009-11/msg00004.html
- lists.opensuse.org/opensuse-security-announce/2010-06/msg00001.html
- rhn.redhat.com/errata/RHSA-2014-0311.html
- rhn.redhat.com/errata/RHSA-2014-0312.html
- secunia.com/advisories/37431
- secunia.com/advisories/37682
- secunia.com/advisories/37683
- secunia.com/advisories/38066
- secunia.com/advisories/38977
- secunia.com/advisories/39001
- secunia.com/secunia_research/2009-35/
- securityreason.com/achievement_securityalert/69
- securityreason.com/achievement_securityalert/71
- securityreason.com/achievement_securityalert/72
- securityreason.com/achievement_securityalert/73
- securityreason.com/achievement_securityalert/75
- securityreason.com/achievement_securityalert/76
Vendor advisories and official records. Exploit/PoC links are deliberately left out.