NotesApplication · Ibm

CVE-2018-1410

HIGH · 7.8 CVSS v3.0 Published 2018-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
IBM Notes Diagnostics (IBM Client Application Access and IBM Notes) could allow a local user to execute commands on the system. By crafting a command line sent via the shared memory IPC, which could be tricked into executing an executable chosen by the attacker. IBM X-Force ID: 138709.

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 confidence

IBM Notes Diagnostics contains a local privilege escalation vulnerability in its shared memory inter-process communication (IPC) mechanism. A local attacker can craft a malicious command line sent via shared memory that tricks the application into executing an attacker-controlled executable with elevated privileges.

MitigationApply the IBM patch for CVE-2018-1410. If patches are unavailable, restrict local user access to systems running IBM Notes Diagnostics and consider disabling the diagnostic service until patched.

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
NotesApplication
Affected:= 8.5.1.5= 8.5.2.4= 8.5.3.6= 9.0= 9.0.1.9
Client Application AccessApplication
Affected:= 1.0.0.1= 1.0.1= 1.0.1.2

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:L/AC:L/PR:L/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed IBM Notes version
    Check the installed version of IBM Notes on the system. This can typically be found in the Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Notes or by examining the program files directory for the notes.exe version properties.
    Affected if The installed version matches 8.5.1.5, 8.5.2.4, 8.5.3.6, 9.0, or 9.0.1.9
  2. Identify installed IBM Client Application Access version
    Check the installed version of IBM Client Application Access. This is usually found in Add/Remove Programs or by examining the installation directory for version information.
    Affected if The installed version matches 1.0.0.1, 1.0.1, or 1.0.1.2
  3. Confirm IBM Notes Diagnostics component is present
    Verify that the IBM Notes Diagnostics component is installed. This component provides diagnostic and troubleshooting functionality and includes the vulnerable shared memory IPC mechanism.
    Affected if The Diagnostics component is installed and available on the system
  4. Check if diagnostic service is accessible to local users
    Examine file system and registry permissions on the IBM Notes data directories and the diagnostic service configuration to determine if non-privileged local users can interact with the shared memory IPC mechanism.
    Affected if Local users without administrator privileges have access to interact with the diagnostic service shared memory interface

You are affected if IBM Notes version 8.5.1.5 through 9.0.1.9 or IBM Client Application Access version 1.0.0.1 through 1.0.1.2 is installed with the Diagnostics component present and accessible to local users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the IBM patch for CVE-2018-1410. If patches are unavailable, restrict local user access to systems running IBM Notes Diagnostics and consider disabling the diagnostic service until patched.

Fix this in Notes Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-1410 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-1410 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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