dbcve.org
Lotus InotesApplication · Ibm

CVE-2010-0274

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
Unspecified vulnerability in the Edit Contact scene in Ultra-light Mode in IBM Lotus iNotes (aka Domino Web Access or DWA) before 229.241 for Domino 8.0.2 FP3 has unknown impact and attack vectors, aka SPR LSHR7TBLY5.

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

IBM Lotus iNotes (Domino Web Access) before version 229.241 for Domino 8.0.2 FP3 contains an unspecified vulnerability in the Edit Contact functionality of Ultra-light Mode. The vulnerability has unknown impact and attack vectors, rated at CVSS 10 (Critical), allowing potential unauthorized access or manipulation of contact information.

MitigationUpgrade IBM Lotus iNotes to version 229.241 or later for Domino 8.0.2 FP3. If upgrading is not feasible, disable Ultra-light Mode in IBM Lotus iNotes and ensure Domino server is behind appropriate network segmentation and authentication controls.

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 installed IBM Lotus iNotes version
    Check the iNotes version by logging into Domino Web Access and navigating to Help > About, or by querying the Domino server's iNotes installation directory for version information. Alternatively, check the Domino server document in the Domino Directory for the iNotes version field.
    Affected if The installed version matches one of the affected versions: 229.011, 229.021, 229.031, 229.041, 229.051, 229.061, 229.101, 229.111, 229.131, 229.141, 229.151, or any version <= 229.231 before the fixed version 229.241.
  2. Confirm Domino server version and fix pack level
    Run the command 'show server' on the Domino console or check the server's About document to verify the Domino version is 8.0.2 with Fix Pack 3 (FP3) installed.
    Affected if The Domino server is version 8.0.2 FP3 and the iNotes version is vulnerable per step 1.
  3. Determine if Ultra-light Mode is enabled
    Check the iNotes configuration on the Domino server: open the Domino Directory, locate the Server document, and inspect the iNotes settings for Ultra-light Mode (also known as Ultralite). This can also be checked via the iNotes URL parameter 'ui=ultralite' or by examining the user's iNotes preferences.
    Affected if Ultra-light Mode is enabled and the iNotes/Domino version is in the affected range.
  4. Verify Edit Contact functionality is accessible
    Log into iNotes in Ultra-light Mode and navigate to the Contacts section to confirm the Edit Contact feature is available and accessible.
    Affected if Ultra-light Mode is active with Edit Contact functionality accessible on a vulnerable version.

You are affected if IBM Lotus iNotes version is 229.241 or lower on Domino 8.0.2 FP3 and Ultra-light Mode is enabled, allowing access to the Edit Contact feature in iNotes.

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. If upgrading is not feasible, disable Ultra-light Mode in IBM Lotus iNotes and ensure Domino server is behind appropriate network segmentation and authentication controls.

Recommended fix High confidence

IBM Lotus iNotes 229.241 or later for Domino 8.0.2 FP3

  1. 1. Identify all IBM Lotus Domino servers running iNotes (Domino Web Access) with versions 229.231 or lower, or versions 229.011, 229.021, or 229.031
  2. 2. Review the current IBM Lotus Domino version to confirm it is 8.0.2 FP3 (Fix Pack 3)
  3. 3. Download IBM Lotus iNotes version 229.241 or later from IBM Fix Central (fixcentral.alphaworks.ibm.com)
  4. 4. Apply the upgrade following IBM's standard Domino/iNotes upgrade procedures
  5. 5. After upgrade, verify the iNotes version displays 229.241 or higher in the About section
  6. 6. Test the Edit Contact functionality in Ultra-light Mode to confirm normal operation

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

Fix this in Lotus Inotes Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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