dbcve.org
Lotus InotesApplication · Ibm

CVE-2010-0918

HIGH · 10.0 CVSS v2.0 Published 2010-03-03
Fix available
A fix is available. Upgrade to after 229.271 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Multiple unspecified vulnerabilities in the UltraLite functionality in IBM Lotus iNotes (aka Domino Web Access or DWA) before 229.281 for Domino 8.0.2 FP4 have unknown impact and attack 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 · low confidence

Multiple unspecified vulnerabilities exist in the UltraLite functionality of IBM Lotus iNotes (Domino Web Access) prior to version 229.281 for Domino 8.0.2 FP4. The exact nature of these vulnerabilities, their attack vectors, and potential impact are not disclosed in the available information.

MitigationUpgrade IBM Lotus iNotes/DWA to version 229.281 or later for Domino 8.0.2 FP4 to resolve the UltraLite vulnerabilities.

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
Lotus InotesApplication
Affected:<= 229.271= 229.011= 229.021= 229.031= 229.041= 229.051= 229.061= 229.101= 229.111= 229.131= 229.141= 229.151

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
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/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 checks

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

  1. Confirm IBM Lotus iNotes (Domino Web Access) is installed
    Check for iNotes installation by looking for Domino server with iNotes component, typically found in the Domino program directory or via Domino console command 'show server'
    Affected if iNotes is not present on the server
  2. Identify the iNotes build version
    Access the Domino console or check the iNotes installation directory for version information. The build version format appears as a 3-digit number such as 229.x
    Affected if The build version cannot be determined or is below 229.281
  3. Compare installed version against affected ranges
    Check if the installed iNotes version is either <= 229.271 or exactly matches one of these: 229.011, 229.021, 229.031, 229.041, 229.051, 229.061, 229.101, 229.111, 229.131, 229.141, 229.151
    Affected if The installed version matches any of these affected version numbers or is 229.271 or lower
  4. Verify UltraLite functionality is enabled
    Check iNotes configuration files (typically in the Domino data directory under iNotes) or Domino server documents for UltraLite plugin/enablement settings
    Affected if UltraLite is enabled and the version check above shows an affected version

A server is affected if it runs IBM Lotus iNotes with a version at or below 229.271 (or any of the specific versions listed) AND has the UltraLite functionality enabled.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 229.271
Interim mitigation

Upgrade IBM Lotus iNotes/DWA to version 229.281 or later for Domino 8.0.2 FP4 to resolve the UltraLite vulnerabilities.

Recommended fix High confidence

IBM Lotus iNotes 229.281 or later for Domino 8.0.2 FP4

  1. Identify the current IBM Lotus iNotes version by checking the Domino server version and iNotes installation
  2. Confirm the Domino server is at version 8.0.2 FP4 or later before upgrading iNotes
  3. Download IBM Lotus iNotes version 229.281 or later from IBM Fix Central or your IBM entitlement
  4. Apply the iNotes upgrade following IBM's standard upgrade procedures for Domino Web Access
  5. Verify the installation by checking the iNotes version shows 229.281 or higher
  6. Restart the Domino server to ensure all iNotes components load with the updated version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lotus Inotes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0918 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2010-0918 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