dbcve.org
Lotus Quickr For DominoApplication · Ibm

CVE-2013-6748

HIGH · 7.5 CVSS v2.0 Published 2014-01-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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 ActiveX control in qp2.cab in IBM Lotus Quickr for Domino 8.5.1 before 8.5.1.42-001b allows remote attackers to execute arbitrary code via a crafted HTML document, a different vulnerability than CVE-2013-6749.

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 ActiveX control (qp2.cab) in IBM Lotus Quickr for Domino 8.5.1 allows remote attackers to execute arbitrary code via a crafted HTML document. The flaw affects versions prior to 8.5.1.42-001b and is a distinct vulnerability from CVE-2013-6749.

MitigationUpdate IBM Lotus Quickr for Domino to version 8.5.1.42-001b or later. If immediate patching is not feasible, disable the qp2.cab ActiveX control or implement network-level restrictions to block malicious HTML vectors.

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.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
Low
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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. Verify IBM Lotus Quickr for Domino installation
    Check the installed version of IBM Lotus Quickr for Domino through the Domino Administrator client, the product installation directory, or by querying the Domino server via HTTP (e.g., /qp/html/databases.nsf), and locate the version information typically displayed in the product About or Readme files.
    Affected if The installed version is 8.5.1 and is prior to 8.5.1.42-001b
  2. Locate the qp2.cab ActiveX control file
    Search the IBM Lotus Quickr for Domino installation directory for the presence of qp2.cab file. This file is typically found in the Quickr data or html directories accessible via the Domino server.
    Affected if The qp2.cab file exists in the Quickr installation directory, indicating the vulnerable ActiveX component is present
  3. Check ActiveX control registration status
    On Windows systems running the Quickr client or server, examine the Windows registry for registration of the qp2 ActiveX control (clsid values related to qp2.cab) or use browser add-on management to verify if the control is enabled in Internet Explorer.
    Affected if The qp2 ActiveX control is registered and enabled in the browser or Windows system, making the vulnerability exploitable through malicious HTML content
  4. Compare version against affected range
    Review the exact version string identified in step 1 and compare it to the known affected range: versions 8.5.1 prior to 8.5.1.42-001b.
    Affected if The installed version falls within the vulnerable range (8.5.1 versions earlier than 8.5.1.42-001b)
  5. Inspect HTML content handling
    Verify whether the Quickr server processes or serves HTML content that could contain embedded calls to the qp2.cab ActiveX control, particularly in Quickr places or teamrooms.
    Affected if The Quickr server serves HTML content and users can access it via web browsers, providing a potential attack vector for the ActiveX buffer overflow

A user is affected if IBM Lotus Quickr for Domino version 8.5.1 is installed with the qp2.cab ActiveX control present and the version is earlier than 8.5.1.42-001b.

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

Update IBM Lotus Quickr for Domino to version 8.5.1.42-001b or later. If immediate patching is not feasible, disable the qp2.cab ActiveX control or implement network-level restrictions to block malicious HTML vectors.

Fix this in Lotus Quickr For Domino Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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 locally
dbcve dependency scanner

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