dbcve.org
Lotus DominoApplication · Ibm

CVE-2007-0068

HIGH · 9.3 CVSS v2.0 Published 2007-06-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
IBM Lotus Domino 7.0.x before 7.0.3 does not revalidate the signature on a signed scheduled agent after the agent is modified, which allows remote authenticated users to gain privileges via a modified agent in a server database.

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 Lotus Domino 7.0.x before 7.0.3 fails to revalidate digital signatures on scheduled agents after modification. This allows authenticated remote users to modify signed agents in server databases, executing potentially malicious code with the privileges of the original signer, effectively enabling privilege escalation.

MitigationUpgrade IBM Lotus Domino to version 7.0.3 or later. Review all scheduled agents in server databases for unauthorized modifications and ensure only trusted signers have agent creation/modification permissions.

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 DominoApplication
Affected:= 7.0= 7.0.1= 7.0.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
Network
Complexity
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/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 Lotus Domino version
    Use the Domino console command 'show version' or check the program files for the installed Domino version number
    Affected if The version displayed is 7.0, 7.0.1, or 7.0.2 (versions before 7.0.3)
  2. Confirm scheduled agents exist
    Access the Domino Administrator and browse to the databases on the server, then view the agent list for each database to identify scheduled agents
    Affected if Scheduled agents are present on the server in any database
  3. Check agent modification permissions
    Review the ACL (Access Control List) settings for each database containing scheduled agents, looking for roles or user permissions that allow agent modification
    Affected if Any authenticated users have permission to modify or create agents in databases containing scheduled agents
  4. Inspect agent signatures
    Open the scheduled agents in Domino Designer and check the 'Run as web user' setting and the agent signer field for each scheduled agent
    Affected if Scheduled agents run with elevated privileges and are signed by accounts other than the current administrator

You are affected if you are running Lotus Domino version 7.0, 7.0.1, or 7.0.2 and have scheduled agents on the server where non-trusted users have modification permissions.

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

Upgrade IBM Lotus Domino to version 7.0.3 or later. Review all scheduled agents in server databases for unauthorized modifications and ensure only trusted signers have agent creation/modification permissions.

Recommended fix High confidence

Lotus Domino 7.0.3

  1. 1. Back up the current IBM Lotus Domino server data and configuration.
  2. 2. Download IBM Lotus Domino version 7.0.3 or later from IBM's official support site.
  3. 3. Review IBM's upgrade documentation for version 7.0.x to 7.0.3.
  4. 4. Stop the Domino server services.
  5. 5. Install IBM Lotus Domino 7.0.3 or later on the server.
  6. 6. Verify the server starts successfully after the upgrade.
  7. 7. Test that signed scheduled agents now properly revalidate signatures when modified.
  8. 8. Monitor the server logs for any post-upgrade issues.
Caveat Standard upgrade risks apply - test in non-production environment first; review IBM's release notes for any configuration or compatibility changes in 7.0.3

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

Fix this in Lotus Domino Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,440
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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