dbcve.org
Lotus Quickr For DominoApplication · Ibm

CVE-2013-3026

HIGH · 9.3 CVSS v2.0 Published 2013-06-17
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
Buffer overflow in the Lotus Quickr for Domino ActiveX control in qp2.cab in IBM Lotus Quickr 8.1 before FP 8.1.0.32-001a, 8.2 before FP 8.2.0.28-001a, and 8.5.1 before FP 8.5.1.39-002a for Domino allows remote attackers to execute arbitrary code via a crafted web site.

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

Buffer overflow vulnerability in the IBM Lotus Quickr for Domino ActiveX control (qp2.cab) allows remote attackers to execute arbitrary code via a crafted website. The vulnerability affects multiple versions (8.1 before FP 8.1.0.32-001a, 8.2 before FP 8.2.0.28-001a, and 8.5.1 before FP 8.5.1.39-002a) and is exploited through malicious web pages targeting the vulnerable ActiveX component.

MitigationApply the vendor-supplied fix packs (FP 8.1.0.32-001a, FP 8.2.0.28-001a, or FP 8.5.1.39-002a or later). If immediate patching is not possible, disable or restrict the affected ActiveX control via browser security settings or network-level access controls to prevent malicious web-based exploitation.

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 Quickr For DominoApplication
Affected:= 8.1.0= 8.2.0= 8.5.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
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. Locate IBM Lotus Quickr for Domino installation
    Search the system for the Quickr installation directory, typically found under C:\Program Files\IBM\Lotus\Quickr or check Windows registry under HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Lotus\Quickr for the InstallPath value
    Affected if The product is not installed on the system
  2. Determine installed version
    Locate the version file within the Quickr installation directory or check the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\IBM\Lotus\Quickr\CurrentVersion for the version value
    Affected if The version is 8.1.0, 8.2.0, or 8.5.1 without the corresponding fix packs (FP 8.1.0.32-001a, FP 8.2.0.28-001a, or FP 8.5.1.39-002a)
  3. Verify ActiveX control presence
    Search for qp2.cab or qp2.dll in the Quickr installation directory, typically under the domino\html\code directory
    Affected if The qp2.cab or qp2.dll ActiveX control file exists on the system
  4. Check ActiveX control registration
    Open Internet Explorer, go to Tools > Manage Add-ons, and look for the Quickr ActiveX control or query the Windows registry under HKEY_CLASSES_ROOT for entries containing 'Quickr' or 'qp2'
    Affected if The ActiveX control is registered and enabled in Internet Explorer

A user is affected if they have an unpatched version of Lotus Quickr for Domino (8.1.0, 8.2.0, or 8.5.1 before the specified fix packs) installed with the qp2 ActiveX control present and enabled in their browser.

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

Apply the vendor-supplied fix packs (FP 8.1.0.32-001a, FP 8.2.0.28-001a, or FP 8.5.1.39-002a or later). If immediate patching is not possible, disable or restrict the affected ActiveX control via browser security settings or network-level access controls to prevent malicious web-based exploitation.

Recommended fix High confidence

Lotus Quickr 8.1 to FP 8.1.0.32-001a+, or 8.2 to FP 8.2.0.28-001a+, or 8.5.1 to FP 8.5.1.39-002a+

  1. 1. Identify the current installed version of Lotus Quickr for Domino (8.1, 8.2, or 8.5.1)
  2. 2. For Lotus Quickr 8.1: Upgrade to Fix Pack 8.1.0.32-001a or later
  3. 3. For Lotus Quickr 8.2: Upgrade to Fix Pack 8.2.0.28-001a or later
  4. 4. For Lotus Quickr 8.5.1: Upgrade to Fix Pack 8.5.1.39-002a or later
  5. 5. Obtain the appropriate Fix Pack from IBM Support (www-01.ibm.com)
  6. 6. Apply the Fix Pack following IBM's standard upgrade procedures for Lotus Quickr for Domino
  7. 7. Verify the version after upgrade to confirm the patch was applied successfully
Caveat Review IBM release notes for the specific Fix Pack for any compatibility notes or known issues before applying

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

Fix this in Lotus Quickr For Domino Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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