CVE-2007-6593
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 · uneditedMultiple stack-based buffer overflows in l123sr.dll in Autonomy (formerly Verity) KeyView SDK, as used by IBM Lotus Notes 5.x through 8.x, allow user-assisted remote attackers to execute arbitrary code via the (1) Length and (2) Value fields for certain Types in a Lotus 1-2-3 (.123) file in the Worksheet File (WKS) format, as demonstrated by a file with a crafted SRANGE record, a different vulnerability than CVE-2007-5909.
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 confidenceStack-based buffer overflow in l123sr.dll (Autonomy KeyView SDK) allows arbitrary code execution when IBM Lotus Notes 5.x-8.x parses a malicious Lotus 1-2-3 (.123) file. The vulnerability is triggered via crafted Length and Value fields in an SRANGE record within WKS format files.
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= 5.0= 6.0= 6.5= 7.0= 8.0CVSS 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
- None
AV:N/AC:M/Au:N/C:C/I:C/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Verify IBM Lotus Notes installationLocate the IBM Lotus Notes executable (notes.exe) on the system and confirm it is presentAffected if Lotus Notes is not installed, the system is not affected by this CVE
-
Check installed Lotus Notes versionRun 'notes.exe -version' or check the version property of the notes.exe file in the installation directoryAffected if The installed version is 5.0, 6.0, 6.5, 7.0, or 8.0, indicating it falls within the affected version range
-
Locate the vulnerable l123sr.dll componentSearch for the file l123sr.dll within the Lotus Notes installation directory structure, particularly within KeyView SDK subdirectoriesAffected if The l123sr.dll file exists in the Lotus Notes installation, confirming the vulnerable component is present
-
Confirm KeyView SDK is presentIdentify whether the Autonomy KeyView SDK components are installed as part of the Lotus Notes installation by checking for KeyView-related directories or DLLsAffected if The KeyView SDK is present and includes the vulnerable l123sr.dll, making parsing of Lotus 1-2-3 files potentially exploitable
The environment is affected if IBM Lotus Notes versions 5.0 through 8.0 are installed with the vulnerable l123sr.dll component from the Autonomy KeyView SDK present and capable of parsing .123 files.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor patches from IBM/Lotus Notes to obtain an updated KeyView SDK with patched l123sr.dll, or upgrade to a Lotus Notes version beyond 8.x that includes the fix.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-6593 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2007-6593 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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