01 Record
CVE-2007-4315
The AMD ATI atidsmxx.sys 3.0.502.0 driver on Windows Vista allows local users to bypass the driver signing policy, write to arbitrary kernel memory locations, and thereby gain privileges via
UnratedPUBLISHEDCNA: mitre
CNA base scoreUnratedNo CNA CVSS vector
02 Description
The AMD ATI atidsmxx.sys 3.0.502.0 driver on Windows Vista allows local users to bypass the driver signing policy, write to arbitrary kernel memory locations, and thereby gain privileges via
03 Exploitation and scoring
- Exploitation
- Not assessed. CISA has not published an exploitation assessment for this record, and it is not in the KEV catalog. That is an absence of assessment, not a finding of no risk.
- SSVC decision
- Not assessed by CISA
- EPSS probability
- 0.29% probability of exploitation activity in the next 30 days.
- EPSS percentile
- Equal to or higher than the score of 21.9% of scored records. A rank, not a probability.
- NVD base score
- The NVD has published no score for this record
- NVD CVSS vector
- No NVD score to derive
- NVD analysis status
- Modified. NVD last modified this record on 2026-06-16.
- Red Hat severity
- No Red Hat rating. Red Hat rates the CVEs that affect its products.
Exploit-prediction scores from FIRST. Independent scoring and analysis status from the NVD. Vendor severity from Red Hat. Exploitation assessment and catalog membership from CISA.
04 Metadata
- Published
- 2007-08-13 21:00Z19 YR AGO
- Last updated
- 2024-08-07 14:53Z2 YR AGO
- Reserved
- 2007-08-13
- Assigning CNA
- mitre
- Record state
- PUBLISHED
- Severity
- Not rated by the issuing CNA
- CNA CVSS vector
- Not published by the issuing CNA
- Weaknesses
- Data version
- 5.1
- Document digest
- 08f651008501a55829aef81c3b48d38b9ced4b2ecfc0d1d832517d8a82c60bd8
05 Affected products
VendorProductVersionsPlatforms
06 References
- secunia.com26448http://secunia.com/advisories/26448
- blogs.zdnet.comhttp://blogs.zdnet.com/security/?p=438
- www.securityfocus.com25265http://www.securityfocus.com/bid/25265
- blogs.zdnet.comhttp://blogs.zdnet.com/security/?p=427