CVE-2010-1795
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedUntrusted search path vulnerability in Apple iTunes before 9.1, when running on Windows 7, Vista, and XP, allows local users and possibly remote attackers to gain privileges via a Trojan horse DLL in the current working directory.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThis is a DLL hijacking (untrusted search path) vulnerability in Apple iTunes versions prior to 9.1 running on Windows 7, Vista, and XP. When iTunes executes, it loads dynamic link libraries from the current working directory before checking system directories, allowing an attacker who can place a malicious DLL in the same directory as iTunes to achieve code execution with the privileges of the user running iTunes, potentially leading to privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0= 1.1.1= 1.1.2= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 3.0.0= 3.0.1= 4.0.0= 4.0.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- M
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:N/C:C/I:C/A:C
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if Apple iTunes is installedOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\iTunes.exe, or look for iTunes in Program Files folderAffected if iTunes executable is found on the system
-
Identify installed iTunes versionRight-click iTunes in the Start menu and select Properties, or use command: reg query "HKEY_LOCAL_MACHINE\SOFTWARE\Apple Computer, Inc.\iTunes" /v VersionAffected if Returned version is lower than 9.1 (such as 9.0.x, 4.x, 3.x, 2.x, or 1.x)
-
Verify Windows versionRun 'winver' or check System PropertiesAffected if Running Windows XP, Vista, or Windows 7 (the OS versions mentioned as affected)
-
Confirm vulnerable DLL search path behaviorAttempt to launch iTunes from a directory writable by other users, or inspect iTunes executable with a tool like Process Monitor to observe DLL loading behaviorAffected if iTunes attempts to load DLLs from the current working directory before system directories
User is affected if iTunes version 9.0 or earlier is installed on Windows XP, Vista, or 7 and the application can be launched from or can load DLLs from directories outside the system paths.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpdate Apple iTunes to version 9.1 or later, which includes proper DLL search path handling. Alternatively, ensure iTunes is launched from trusted directories and avoid running it from directories writable by other users.
iTunes 9.1 or later
- Download and install iTunes 9.1 or later from the official Apple website (support.apple.com)
- After installation, verify the installed version by opening iTunes and going to Help > About iTunes
- Confirm the version number is 9.1 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1795 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-1795 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data