CVE-2005-1528
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 the crttrap command in QNX Neutrino RTOS 6.2.1 allows local users to load arbitrary libraries via a LD_LIBRARY_PATH environment variable that references a malicious library.
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 confidenceThe crttrap command in QNX Neutrino RTOS 6.2.1 suffers from an untrusted search path vulnerability where it loads libraries from paths specified in the LD_LIBRARY_PATH environment variable without validation. A local attacker can exploit this by setting LD_LIBRARY_PATH to point to a directory containing a maliciously crafted library with the same name as a legitimate library the tool expects to load, causing arbitrary code execution with the privileges of the crttrap command.
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= 6.2.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
- Local
- Complexity
- Low
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:L/AC:L/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.
-
Verify the QNX Neutrino RTOS versionRun 'uname -a' or check system information to confirm the operating system version is 6.2.1Affected if The system is running QNX Neutrino RTOS version 6.2.1
-
Locate the crttrap commandExecute 'which crttrap' or 'find / -name crttrap 2>/dev/null' to find the crttrap binary on the systemAffected if The crttrap command exists on the system
-
Check library dependencies of crttrapRun 'ldd /path/to/crttrap' (if available on QNX) or examine what shared libraries crttrap links againstAffected if crttrap loads shared libraries that could be intercepted via LD_LIBRARY_PATH
-
Inspect LD_LIBRARY_PATH environment variableRun 'echo $LD_LIBRARY_PATH' to see if the environment variable is setAffected if LD_LIBRARY_PATH is set and contains writable directories accessible to the user running crttrap
-
Check for untrusted directory permissions in LD_LIBRARY_PATHReview each directory in LD_LIBRARY_PATH for world-writable or group-writable permissions using 'ls -la' on each pathAffected if Any directory in LD_LIBRARY_PATH is writable by untrusted users, allowing them to place malicious library files
A user is affected if running QNX Neutrino RTOS 6.2.1 with the crttrap command present and LD_LIBRARY_PATH set to include directories writable by untrusted users.
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 dataFix the crttrap command to use absolute library paths, remove dependency on LD_LIBRARY_PATH, or validate/sanitize the library path environment before use. Alternatively, ensure LD_LIBRARY_PATH is not used in secure deployment contexts and that only trusted library directories are accessible.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2005-1528 — 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-2005-1528 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