CVE-2013-0487
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 · uneditedThe Java Console in IBM Domino 8.5.x allows remote authenticated users to hijack temporary credentials by leveraging knowledge of configuration details, aka SPR KLYH8TNNDN.
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 confidenceThe Java Console in IBM Domino 8.5.x contains a vulnerability where remote authenticated users can hijack temporary credentials by obtaining knowledge of configuration details. This allows attackers to impersonate legitimate users by leveraging exposed or guessable configuration information that governs temporary credential generation or storage.
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= 8.5.0= 8.5.0.1= 8.5.1= 8.5.1.1= 8.5.1.2= 8.5.1.3= 8.5.1.4= 8.5.1.5= 8.5.2.0= 8.5.2.1= 8.5.2.2= 8.5.2.3CVSS 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
- Single
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:M/Au:S/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 Domino versionRun 'tell server version' on the Domino console or check the installed product version through the IBM Domino installationAffected if The installed version matches any of: 8.5.0, 8.5.0.1, 8.5.1, 8.5.1.1, 8.5.1.2, 8.5.1.3, 8.5.1.4, 8.5.1.5, 8.5.2.0, 8.5.2.1, 8.5.2.2, or 8.5.2.3
-
Confirm Java Console is enabledCheck the Domino server document in the Directory, under Server Setup - Java Console tab, or run 'show config' and look for JavaConsoleEnable settingsAffected if Java Console is enabled on the server (JavaConsoleEnable=1 or similar setting present)
-
Inspect Java Console configuration for credential exposureReview the notes.ini file or Java Console configuration files for parameters controlling temporary credential generation or storage, such as those containing keys, tokens, or session-related settingsAffected if Configuration contains exposed or weakly protected credential-related parameters (temporary passwords, session tokens, or authentication keys)
-
Check access controls on Java ConsoleReview ACL settings and server access groups in the Domino Directory to determine which authenticated users can access the Java ConsoleAffected if Java Console is accessible to authenticated users beyond trusted administrators
You are affected if running a listed IBM Domino 8.5.x version with the Java Console enabled and accessible, especially if credential-related configuration settings are exposed or accessible to non-administrative authenticated 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 dataApply the relevant IBM Domino patch or upgrade to a supported version. Review and secure Java Console configuration to prevent exposure of credential-related settings, and limit access to the Java Console to trusted authenticated users only.
- 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-2013-0487 — 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-0487 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