Access SupportHardware / appliance · Lenovo

CVE-2007-2240

MEDIUM · 5.8 CVSS v2.0 Published 2007-08-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
67/100
Remediation priority · Elevated
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 IBM Lenovo Access Support acpRunner ActiveX control, as distributed in acpcontroller.dll before 1.2.8.0 and possibly acpir.dll before 1.0.0.9 (Automated Solutions 1.0 before fix pack 1), does not properly validate digital signatures of downloaded software, which makes it easier for remote attackers to spoof a download.

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 acpRunner ActiveX control in IBM Lenovo Access Support (acpcontroller.dll before 1.2.8.0) fails to properly validate digital signatures on downloaded software, allowing remote attackers to spoof legitimate downloads and inject malicious code onto affected systems.

MitigationUpdate acpcontroller.dll to version 1.2.8.0 or later, or disable the vulnerable ActiveX control through Internet Explorer add-on settings or registry restrictions.

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
Access SupportHardware / appliance
Affected:all versions
Automated SolutionsHardware / appliance
Affected:= 1.0

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
None
Integrity
Partial
Availability
Partial

AV:N/AC:M/Au:N/C:N/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. Check if Lenovo Access Support is installed
    Open Control Panel > Programs and Features and look for 'Lenovo Access Support' or 'Lenovo Automated Solutions', or search for acpcontroller.dll using Windows Explorer search
    Affected if Either Lenovo Access Support (any version) or Lenovo Automated Solutions version 1.0 is present on the system
  2. Locate and identify acpcontroller.dll version
    Find acpcontroller.dll in the Lenovo Access Support installation directory (typically in C:\Program Files\Lenovo\Access Support\ or C:\Program Files\IBM\IBM Access Support\), right-click the file, select Properties, and view the Version tab
    Affected if The file version shown is earlier than 1.2.8.0 or the version field is missing or cannot be determined
  3. Verify the ActiveX control is registered
    Open Internet Explorer, go to Tools > Manage Add-ons, and look for 'acpRunner' or 'acpController' in the ActiveX controls list, or check the registry under HKLM\SOFTWARE\Microsoft\Code Store Database\SPOOL\ for the control registration
    Affected if The acpRunner ActiveX control appears in the list of installed add-ons
  4. Confirm the vulnerability trigger condition
    This vulnerability is triggered when the ActiveX control processes downloaded software without proper digital signature validation - check if the acpcontroller.dll file exists and is reachable by Internet Explorer
    Affected if The acpcontroller.dll file exists and the ActiveX control is enabled in Internet Explorer, allowing it to be invoked by malicious web content

A system is affected if Lenovo Access Support or Lenovo Automated Solutions is installed with acpcontroller.dll version earlier than 1.2.8.0 and the ActiveX control is registered and enabled.

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 acpcontroller.dll to version 1.2.8.0 or later, or disable the vulnerable ActiveX control through Internet Explorer add-on settings or registry restrictions.

Fix this in Access Support Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-2240 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