Shared memory sections and events in IBM DB2 8.1 have default permissions of read and write for the Everyone group, which allows local users
Shared memory sections and events in IBM DB2 8.1 have default permissions of read and write for the Everyone group, which allows local users to gain unauthorized access, gain sensitive information, such as cleartext passwords, and cause a denial of service.
- Published
- Dec 31, 2005
- Updated
- Jun 16, 2026
- EPSS
- 0.8% · 53th percentile
- CWE
- CWE-732
Sign in to follow · You’ll be notified if a followed record enters KEV, gets an exploit or is updated.
Report tools
Action score
28
Monitor
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.8%
Affected systems
| Vendor | Product | CPE |
|---|---|---|
| ibm | db2 universal database | cpe:2.3:a:ibm:db2_universal_database |
| microsoft | windows | cpe:2.3:o:microsoft:windows |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- ibm db2 universal database7.1
- ibm db2 universal database7.2
- ibm db2 universal database8.0
- ibm db2 universal database8.1
Same product
ibm: all recordsOther highest-scoring records for the same primary product.
- CVE-2005-4865Stack-based buffer overflow in call in IBM DB2 7.x and 8.1 allows remote attackers to execute arbitrary code via a long libname.42Plan
- CVE-2007-6048IBM DB2 UDB 9.1 before Fixpak 4 uses incorrect permissions on ACLs for DB2NODES.CFG, which has unknown impact and attack vectors.41Plan
- CVE-2007-6047Unspecified vulnerability in the DB2DART tool in IBM DB2 UDB 9.1 before Fixpak 4 allows attackers to execute arbitrary commands as the DB2 i41Plan
- CVE-2007-6045Unspecified vulnerability in (1) DB2WATCH and (2) DB2FREEZE in IBM DB2 UDB 9.1 before Fixpak 4 has unknown impact and attack vectors.41Plan
- CVE-2007-6051IBM DB2 UDB 9.1 before Fixpak 4 assigns incorrect privileges to the (1) DB2ADMNS and (2) DB2USERS alternative groups, which has unknown impa40Plan
- CVE-2005-0417Unknown "high risk" vulnerability in DB2 Universal Database 8.1 and earlier has unknown impact and attack vectors.40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
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 ×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 | local | 2004-09-01 |
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-486 d
- Published
- TodaySep 30, 2026+7579 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- none
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- None
- Availability impact
- High
Weakness class (CWE)
CWE-732 · Incorrect Permission Assignment for Critical ResourceCVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H
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)
- Accessing Functionality Not Properly Constrained by ACLsCAPEC-1likelihood: High · High
- Privilege AbuseCAPEC-122likelihood: High · Medium
- Directory IndexingCAPEC-127likelihood: High · Medium
- Using Malicious FilesCAPEC-17likelihood: High · Very High
- Exploiting Incorrectly Configured Access Control Security LevelsCAPEC-180likelihood: High · Medium
- Signing Malicious CodeCAPEC-206Very High
- Hijacking a privileged processCAPEC-234Medium
- Reusing Session IDs (aka Session Replay)CAPEC-60likelihood: High · High
ATT&CK techniques
- File and Directory DiscoveryT1083
- Access Token Manipulation:Token Impersonation/TheftT1134.001
- Server Software Component: Terminal Services DLLT1505.005
- Abuse Elevation Control MechanismT1548
- Use Alternate Authentication Material:Web Session CookieT1550.004
- Subvert Trust Controls:Code SigningT1553.002
- Compromise Client Software BinaryT1554
- Hijack Execution Flow:Executable Installer File Permissions WeaknessT1574.005
- Hijack Execution Flow: ServicesFile Permissions WeaknessT1574.010
Noroxi analysis
No Noroxi analysis for this record yet
We don't hand-write analysis for all 385,000+ vulnerabilities; that wouldn't be honest. For notable, high-impact vulnerabilities our team writes the mechanism, detection and remediation steps.
We use this product, ask for helpChange log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
- marc.info/?l=bugtraq&m=110495402231836&w=2
- secunia.com/advisories/12733/
- www-1.ibm.com/support/docview.wss?uid=swg21181228
- www.nextgenss.com/advisories/db205012005F.txt
- www.securityfocus.com/bid/11402
- exchange.xforce.ibmcloud.com/vulnerabilities/17605
Vendor advisories and official records. Exploit/PoC links are deliberately left out.