CVE-2007-3268 json
The TFTP implementation in IBM Tivoli Provisioning Manager for OS Deployment 5.1 before Fix Pack 3 allows remote attackers to cause a denia…
published 2007-07-18 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-3258
- cvss
- 7.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 0
- none known
Summary
The TFTP implementation in IBM Tivoli Provisioning Manager for OS Deployment 5.1 before Fix Pack 3 allows remote attackers to cause a denial of service (rembo.exe crash and multiple service outage) via a read (RRQ) request with an invalid blksize (blocksize), which triggers a divide-by-zero error.
Patch / fix
Exploit prediction
2.23% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 7.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
- Weakness
-
- CWE-369 Divide By Zero
References
-
www3.software.ibm.com
/ibmdl/pub/software/tivoli_support/patches/patches_5.1.0/5.1.0-TIV-TPMOSD-FP0003/5.1.0-TIV-TPMOSD-FP0003.READM
patch
-
secunia.com
/advisories/26093
third-party-advisory, broken-link, patch, vendor-advisory
-
www-1.ibm.com
/support/docview.wss?uid=swg24016347
broken-link, patch
-
labs.idefense.com
/intelligence/vulnerabilities/display.php?id=560
third-party-advisory, broken-link, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/35468
vdb-entry, vendor-advisory
-
vupen.com
/english/advisories/2007/2560
vdb-entry, broken-link
-
securityfocus.com
/bid/24942
vdb-entry, broken-link, third-party-advisory
-
securitytracker.com
/id?1018401
vdb-entry, broken-link, third-party-advisory
Sources
- CVE List CVE-2007-3268
- NVD CVE-2007-3268
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.