CVE-2007-2929
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 · uneditedThe 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), exposes unsafe methods to arbitrary web domains, which allows remote attackers to download arbitrary code onto a client system and execute this code.
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 confidenceThe IBM Lenovo Access Support acpRunner ActiveX control (acpcontroller.dll before 1.2.8.0 and acpir.dll before 1.0.0.9) exposes unsafe methods to arbitrary web domains, allowing remote attackers to download and execute arbitrary code on affected client systems.
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 dataall versions= 1.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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Check if Lenovo Access Support or Lenovo Automated Solutions is installedOpen Windows Control Panel, go to Programs and Features, and look for 'Lenovo Access Support' or 'Lenovo Automated Solutions' in the installed programs listAffected if Either product is present on the system
-
Locate acpcontroller.dll and check its versionSearch for acpcontroller.dll in typical Lenovo installation directories (commonly under C:\Program Files\Lenovo or C:\Program Files (x86)\Lenovo), right-click the file, select Properties, and view the Version tabAffected if The file version is lower than 1.2.8.0 or the file cannot be found (which may indicate an older unpatched install)
-
Locate acpir.dll and check its versionSearch for acpir.dll in the same Lenovo directories, right-click the file, select Properties, and view the Version tabAffected if The file version is lower than 1.0.0.9 or the file cannot be found (which may indicate an older unpatched install)
-
Verify the acpRunner ActiveX control is registered in Internet ExplorerOpen Internet Explorer, go to Tools > Manage Add-ons, and look for 'acpRunner' or 'acpController' in the ActiveX controls listAffected if The ActiveX control appears in the list and is enabled
The system is affected if Lenovo Access Support or Lenovo Automated Solutions 1.0 is installed AND either acpcontroller.dll is below version 1.2.8.0 or acpir.dll is below version 1.0.0.9, with the acpRunner ActiveX control present and enabled in Internet Explorer.
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 dataDisable the vulnerable acpRunner ActiveX control in Internet Explorer or deploy the patched versions (acpcontroller.dll 1.2.8.0+, acpir.dll 1.0.0.9+) and apply Automated Solutions fix pack 1.
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-2929 — 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-2929 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