CVE-2010-1347
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 · uneditedDirector Agent 6.1 before 6.1.2.3 in IBM Systems Director on AIX and Linux uses incorrect permissions for the (1) diruninstall and (2) opt/ibm/director/bin/wcitinst scripts, which allows local users to gain privileges by executing these scripts.
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 confidenceIBM Systems Director Agent 6.1 before 6.1.2.3 on AIX and Linux has insecure file permissions on the diruninstall and opt/ibm/director/bin/wcitinst scripts. Local unprivileged users can execute these scripts to gain elevated privileges, resulting in local 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= 6.1= 6.1.2CVSS 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 IBM Systems Director Agent is installedCheck for the presence of IBM Director installation directories or use package management commands (e.g., 'ls /opt/ibm/director', 'lslpp -l' on AIX, 'rpm -qa | grep director' on Linux)Affected if The product is not installed - the system is not affected by this CVE
-
Confirm the installed versionRun version check commands for IBM Director Agent. On AIX, use 'lslpp -l | grep director' or check version files in /opt/ibm/director. On Linux, use 'rpm -q ibm-director-agent' or check version files in /opt/ibm/directorAffected if The installed version is 6.1 or 6.1.2.x prior to 6.1.2.3 - the version is within the affected range
-
Locate the diruninstall scriptSearch for the diruninstall script using 'find / -name diruninstall -type f 2>/dev/null' or check common locations like /opt/ibm/director/bin/Affected if The script exists on the system - proceed to permission check; if not found, the system may not be vulnerable (script may have been removed or never installed)
-
Check file permissions on diruninstall and wcitinstRun 'ls -la' on the identified script paths (e.g., /opt/ibm/director/bin/wcitinst and the diruninstall script). Examine the permission bits (owner, group, world execute/write permissions)Affected if Any script is world-writable (w in other permissions) or world-executable without proper ownership restrictions - unprivileged local users can execute the script to escalate privileges
A system is affected if IBM Systems Director Agent version 6.1 through 6.1.2.2 is installed AND the diruninstall or wcitinst scripts have overly permissive file permissions allowing unprivileged users to execute them.
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 dataCorrect the file permissions on diruninstall and wcitinst scripts to restrict execution to authorized users only (e.g., chmod 750 or 700), then verify that authorized administrative users can still execute the scripts properly.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-1347 — 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-1347 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