dbcve.org
Lotus InotesApplication · Ibm

CVE-2010-0275

HIGH · 10.0 CVSS v2.0 Published 2010-01-09
Fix available
A fix is available. Upgrade to after 229.231 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
Ultra-light Mode in IBM Lotus iNotes (aka Domino Web Access or DWA) before 229.241 for Domino 8.0.2 FP3 does not properly handle script commands in the status-alerts URL, which has unspecified impact and attack vectors, aka SPR LSHR7TBM58.

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 confidence

Ultra-light Mode in IBM Lotus iNotes (Domino Web Access) before version 229.241 fails to properly sanitize script commands in the status-alerts URL parameter, allowing injection of malicious script content. This affects Domino 8.0.2 FP3 and earlier versions.

MitigationUpgrade IBM Lotus iNotes to version 229.241 or later for Domino 8.0.2 FP3 to patch the vulnerability; alternatively, disable Ultra-light Mode until the update can be applied.

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.231= 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. Identify IBM Lotus iNotes version
    Locate the installed IBM Lotus iNotes or Domino version through the Domino server administration console, program directory, or by checking the iNotes DLL/version file on the server
    Affected if The installed version is 229.231 or lower, or matches any of these specific versions: 229.011, 229.021, 229.031, 229.041, 229.051, 229.061, 229.101, 229.111, 229.131, 229.141, or 229.151
  2. Verify Ultra-light Mode is enabled
    Check the IBM Lotus iNotes configuration settings, typically found in the Domino server's notes.ini or through the Domino Web Administration interface, for the Ultra-light Mode setting
    Affected if Ultra-light Mode is enabled on the server, as this is the specific feature vulnerable to the status-alerts URL parameter injection
  3. Confirm Domino version
    Check the Domino server version through the Domino Administrator client or by querying the Domino server directly for its version number
    Affected if The Domino version is 8.0.2 FP3 or earlier and iNotes is at a vulnerable version

A user is affected if their IBM Lotus iNotes version is 229.231 or lower (or one of the specific affected builds) AND Ultra-light Mode is enabled on the server.

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.231
Interim mitigation

Upgrade IBM Lotus iNotes to version 229.241 or later for Domino 8.0.2 FP3 to patch the vulnerability; alternatively, disable Ultra-light Mode until the update can be applied.

Recommended fix High confidence

IBM Lotus iNotes 229.241 for Domino 8.0.2 FP3

  1. Verify current IBM Lotus iNotes version by checking the Domino server version and iNotes component version
  2. Review IBM Lotus iNotes 229.241 release notes for Domino 8.0.2 FP3 to understand changes and requirements
  3. Schedule maintenance window for the upgrade following standard change management procedures
  4. Download IBM Lotus Domino 8.0.2 FP3 which includes iNotes version 229.241 from IBM Fix Central or authorized distribution channels
  5. Apply the upgrade to the Domino server following IBM's standard upgrade documentation for Domino 8.0.2 FP3
  6. After upgrade, verify iNotes is running version 229.241 or higher by checking the iNotes about page
  7. Test iNotes Ultra-light Mode functionality to confirm the status-alerts URL handling is fixed
Caveat Standard Domino upgrade risks apply - test thoroughly in non-production environment first, particularly custom iNotes templates and integrations

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

Fix this in Lotus Inotes Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-0275 — 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-0275 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