dbcve.org
Lotus NotesApplication · Ibm

CVE-2007-6594

MEDIUM · 6.9 CVSS v2.0 Published 2007-12-28
Fix available
A fix is available. Upgrade to after 8.0.1 or later.
See remediation →
74/100
Remediation priority · Elevated
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 Notes 8 for Linux before 8.0.1 uses (1) unspecified weak permissions for the installation kit obtained through a Notes 8 download and (2) 0777 permissions for the installdata file that is created by setup.sh, which allows local users to gain privileges via a Trojan horse file.

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 Notes 8 for Linux before 8.0.1 has improper file permissions: unspecified weak permissions on the installation kit and overly permissive 0777 permissions on the installdata file created by setup.sh. This allows local unprivileged users to replace files with Trojan horse executables, potentially gaining elevated privileges upon execution by the installation process or other users.

MitigationUpgrade to IBM Lotus Notes 8.0.1 or later. If upgrading is not immediately feasible, manually identify and correct the 0777 permissions on the installdata file and ensure the installation kit has restrictive permissions (e.g., 755 or stricter) to prevent unauthorized modification.

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 NotesApplication
Affected:<= 8.0.1

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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:L/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. Determine IBM Lotus Notes version on Linux
    Run 'ls -la' on the Lotus Notes installation directory (commonly /opt/ibm/lotus or /opt/lotus) and look for a version file, or run 'notes' binary with --version flag if available. Alternatively, check RPM/DEB package version with 'rpm -q lotus-notes' or 'dpkg -l lotus-notes' if installed via package manager.
    Affected if Installed version is 8.0.1 or earlier (versions before 8.0.1)
  2. Locate the Lotus Notes installation kit
    Search for installation kit files in the system: look for files named 'setup.sh', installation tarballs, or disk images in common locations like /tmp, the user's home directory, or the original installation source directory. Use 'find / -name setup.sh 2>/dev/null' or 'find / -name *Lotus*Notes* 2>/dev/null' to locate these files.
    Affected if Installation kit files exist and have permissions weaker than 755 (such as 777 or world-writable)
  3. Identify the installdata file created by setup.sh
    In the Lotus Notes installation directory, search for a file named 'installdata' or similar. Use 'find /opt/ibm/lotus -name "*installdata*" -o -name "*install*data*" 2>/dev/null'. Check the directory where setup.sh was executed if installation was performed.
    Affected if An installdata file exists with 0777 permissions (rwxrwxrwx)
  4. Verify permissions on Lotus Notes installation directory contents
    Run 'ls -la' on the main Lotus Notes installation directory (/opt/ibm/lotus or /opt/lotus) and examine permission strings. Look for any files or directories with world-writable permissions (the third octet is 7, e.g., -rwxrwxrwx).
    Affected if Any executable or configuration files under the installation directory have 0777 permissions, allowing unprivileged users to modify them

A system is affected if IBM Lotus Notes 8.x for Linux is installed at version 8.0.1 or earlier AND either the installation kit files have weak permissions or the installdata file (or any other executable under the install path) has 0777 permissions, allowing unprivileged users to replace them with malicious code.

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
Upgrade available Upgrade to a release after 8.0.1
Interim mitigation

Upgrade to IBM Lotus Notes 8.0.1 or later. If upgrading is not immediately feasible, manually identify and correct the 0777 permissions on the installdata file and ensure the installation kit has restrictive permissions (e.g., 755 or stricter) to prevent unauthorized modification.

Fix this in Lotus Notes Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
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,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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