CVE-2017-17010
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 Content Manager Assistant for PlayStation version 3.55.7671.0901 and earlier allows an attacker to gain privileges via a Trojan horse DLL in an unspecified 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 confidenceContent Manager Assistant for PlayStation versions 3.55.7671.0901 and earlier contains an untrusted search path vulnerability where the application loads DLLs from directories controllable by an attacker. An attacker can place a malicious Trojan horse DLL in a directory included in the application's DLL search path, causing it to be loaded with the application's elevated privileges.
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<= 3.55.7671.0901CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Identify Content Manager Assistant versionLocate the Content Manager Assistant installation and check its file version. Common locations include Program Files or Program Files (x86). Look for the main executable (typically CMA.exe or similar) and view its properties to find the version number.Affected if The installed version is 3.55.7671.0901 or earlier.
-
Examine application directory for unauthorized DLLsInspect the Content Manager Assistant installation directory for any DLL files that were not part of the original installation. Check for recently created or modified DLLs that could have been placed by an attacker.Affected if Unexpected or unknown DLL files exist in the application directory, especially if they have recent modification dates or unusual names.
-
Check for writable directories in DLL search pathIdentify directories included in the application's DLL search path. Verify if any of these directories are user-writable or located in locations where unprivileged users could place files (such as shared folders, download directories, or user-profile folders).Affected if The application loads DLLs from directories writable by non-privileged users.
-
Review DLL loading behaviorUse process monitoring tools or check application logs to observe which DLLs the application attempts to load at startup and during operation. Compare against expected legitimate DLLs.Affected if The application loads DLLs from locations outside the secure system directories.
A user is affected if Content Manager Assistant version 3.55.7671.0901 or earlier is installed AND the application's DLL search path includes directories controllable by an attacker or contains suspicious DLL files.
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.
From vendor dataEnsure the application loads DLLs only from secure, trusted locations by using absolute paths, implementing SafeDllSearchMode, or employing DLL search order hardening to prevent hijacking of the search path.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-17010 — 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-2017-17010 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