CVE-2013-5467
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 · uneditedMonitoring Agent for UNIX Logs 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP09, and 6.2.3 through FP04 and Monitoring Server (ms) and Shared Libraries (ax) 6.2.0 through FP03, 6.2.1 through FP04, 6.2.2 through FP08, 6.2.3 through FP01, and 6.3.0 through FP01 in IBM Tivoli Monitoring (ITM) on UNIX allow local users to gain privileges via unspecified vectors.
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 · moderate confidenceLocal privilege escalation vulnerability in IBM Tivoli Monitoring (ITM) affecting Monitoring Agent for UNIX Logs and Monitoring Server/Shared Libraries across multiple version ranges. Unspecified vectors allow local users to gain 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= 6.2.0= 6.2.1= 6.2.2= 6.2.3= 6.2.0= 6.2.1= 6.2.2= 6.2.3= 6.3.0CVSS 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.
-
Determine if IBM Tivoli Monitoring is installedSearch for ITM installation directories or check for IBM/Tivoli process binaries. Common locations include /opt/IBM/ITM or C:\Program Files\IBM\ITMAffected if ITM software is present on the system
-
Identify installed ITM component versionsCheck version information for Monitoring Agent for UNIX Logs and Monitoring Server components. Consult ITM inventory or use 'itmcmd' command if availableAffected if Any component version is 6.2.0, 6.2.1, 6.2.2, 6.2.3 (UNIX Logs agent) or 6.2.0-6.2.3/6.3.0 (Monitoring Server/shared libraries)
-
Confirm UNIX Logs agent is runningCheck for uxlogs or logfile agent processes running under ITM service account. Inspect process list for IBM Tivoli Monitoring agent componentsAffected if UNIX Logs agent is active on a vulnerable version
-
Verify Monitoring Server component presenceInspect ITM installation for ms (Monitoring Server) and ax (shared libraries) components. Check installation directory structure for these subcomponentsAffected if Monitoring Server or shared libraries exist at vulnerable versions (6.2.0-6.2.3 or 6.3.0)
-
Assess local user access to ITM directoriesReview file permissions on ITM installation directories and bin folders. Determine if non-privileged local users can modify ITM binaries or scriptsAffected if Local unprivileged users have write access to ITM binaries or configuration directories
System is affected if IBM Tivoli Monitoring with Monitoring Agent for UNIX Logs or Monitoring Server components is installed at versions 6.2.0 through 6.2.3 or 6.3.0, and local users have access to the ITM environment.
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 dataApply the specified fix packs (FP03 for 6.2.0, FP04 for 6.2.1, FP09 for 6.2.2, FP04 for 6.2.3, FP01 for 6.3.0) and restrict local system access to trusted administrative users only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-5467 — 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-2013-5467 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