CVE-2007-1413 in the critical feed json
Buffer overflow in the snmpget function in the snmp extension in PHP 5.2.3 and earlier, including PHP 4.4.6 and probably other PHP 4 versio…
published 2007-03-12 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-1407
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 11.2%
- EPSS 11.2% chance of exploitation in 30 days, percentile 95%
- public exploits
- 3
- Exploit-DB
Summary
Buffer overflow in the snmpget function in the snmp extension in PHP 5.2.3 and earlier, including PHP 4.4.6 and probably other PHP 4 versions, allows context-dependent attackers to execute arbitrary code via a long value in the third argument (object id).
Timeline
- First public exploit (EDB-3439)
- Published
Exploit prediction
11.25% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-4274 PHP 5.2.3 - 'snmpget()' object id Local Buffer Overflow (EDI) local, 2007-08-09
- EDB-4204 PHP 5.2.3 - 'snmpget()' Object id Local Buffer Overflow local, 2007-07-20
- EDB-3439 PHP 4.4.6 - 'snmpget()' Object id Local Buffer Overflow local, 2007-03-09
- securityfocus.com http://www.securityfocus.com/bid/22893 referenced PoC, tagged "exploit" by a source, unverified
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
- Technology feeds
References
-
exploit-db.com
/exploits/4204
exploit
-
exploit-db.com
/exploits/3439
exploit
-
securityfocus.com
/bid/22893
vdb-entry, exploit
-
exchange.xforce.ibmcloud.com
/vulnerabilities/35517
vdb-entry
- retrogod.altervista.org /php_446_snmpget_local_bof.html
-
secunia.com
/advisories/24440
third-party-advisory
Sources
- CVE List CVE-2007-1413
- NVD CVE-2007-1413
Fencer Vulns 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.