dbcve.org
Lotus SametimeApplication · Ibm

CVE-2007-1784

HIGH · 9.3 CVSS v2.0 Published 2007-03-31
Fix available
A fix is available. Upgrade to after 7.0 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
The JNILoader ActiveX control (STJNILoader.ocx) 3.1.0.26 in IBM Lotus Notes Sametime before 7.5 allows remote attackers to load arbitrary DLL libraries and execute arbitrary code via arbitrary arguments to the loadLibrary function.

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

The JNILoader ActiveX control (STJNILoader.ocx) version 3.1.0.26 in IBM Lotus Notes Sametime before 7.5 contains a flaw in its loadLibrary function that allows remote attackers to load arbitrary DLL libraries and execute arbitrary code via crafted arguments.

MitigationUpgrade IBM Lotus Notes Sametime to version 7.5 or later to obtain the patched ActiveX control, or disable the STJNILoader.ocx ActiveX control as a compensating control.

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 SametimeApplication
Affected:<= 7.0= 7.5

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. Confirm IBM Lotus Notes Sametime installation
    Check the Windows registry or Program Files directory for IBM Lotus Notes Sametime installation. Look in HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Lotus\Sametime or HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Sametime for version information.
    Affected if The installed version is 7.0 or earlier, or version 7.5 with the vulnerable ActiveX control.
  2. Locate STJNILoader.ocx file
    Search for STJNILoader.ocx in the Sametime installation directory (typically under Program Files\IBM\Lotus\Sametime or Program Files\IBM\Sametime) and the Windows\System32 directory.
    Affected if The file exists in either location.
  3. Get STJNILoader.ocx version
    Right-click the STJNILoader.ocx file, select Properties, and view the Version tab to obtain the file version. Alternatively, use the command: reg query "HKCR\CLSID" /s | findstr -i "STJNILoader" to locate the registered CLSID, then check the version.
    Affected if The file version is 3.1.0.26 (the vulnerable version).
  4. Check if ActiveX control is registered
    Open the registry and check HKEY_CLASSES_ROOT\STJNILoader.STJNILoader or HKEY_CLASSES_ROOT\CLSID\{CLSID for STJNILoader} to see if the control is registered in Internet Explorer.
    Affected if The ActiveX control is registered and enabled in the browser.

A user is affected if IBM Lotus Notes Sametime 7.0 or earlier, or version 7.5 is installed AND the STJNILoader.ocx file version 3.1.0.26 is present and the ActiveX control is registered.

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 7.0
Interim mitigation

Upgrade IBM Lotus Notes Sametime to version 7.5 or later to obtain the patched ActiveX control, or disable the STJNILoader.ocx ActiveX control as a compensating control.

Recommended fix Moderate confidence

IBM Lotus Sametime 7.5.1 or later (latest stable release)

  1. 1. Identify the current IBM Lotus Sametime version installed in the environment
  2. 2. Upgrade from affected versions (7.0 or earlier, or 7.5) to Sametime 7.5.1 or later (preferably the latest available stable release)
  3. 3. Verify the STJNILoader.ocx ActiveX control version after upgrade to confirm it has been patched or replaced
  4. 4. Test that the Sametime client functionality works correctly after the upgrade
  5. 5. Deploy the updated version organization-wide following standard change management procedures
Caveat Minor: Ensure compatibility with existing Sametime server infrastructure and any third-party integrations before deploying

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

Fix this in Lotus Sametime Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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