# CVE-2014-2956: Missing authorization in n/a

> Remote attackers can execute arbitrary programs via a crafted website due to missing domain-based access control in the AVG ScriptHelper ActiveX control.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 8 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p3rw-869q-ccjh

## What is CVE-2014-2956?

CVE-2014-2956 is a critical missing authorization vulnerability in n/a, published on 8 Jul 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

ScriptHelperApi in the AVG ScriptHelper ActiveX control in ScriptHelper.exe in AVG Secure Search toolbar before 18.1.7.598 and AVG Safeguard before 18.1.7.644 does not implement domain-based access control for method calls, which allows remote attackers to trigger the downloading and execution of arbitrary programs via a crafted web site.

Weakness: CWE-264

## Which versions are affected by CVE-2014-2956?

It affects 2 products.


Products: Avg Safeguard, Avg Secure Search Toolbar.

## How do I fix CVE-2014-2956?

No fix has been published for CVE-2014-2956 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-2956 being exploited?

There is no known exploitation of CVE-2014-2956 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-2956 and fix it if it is affected.

What it is: CVE-2014-2956 is a critical missing authorization vulnerability in n/a, published on 8 Jul 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-2956 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-2956/ (Markdown: https://insights.sbomify.com/CVE-2014-2956/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-2956
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-2956
- OSV: https://osv.dev/vulnerability/CVE-2014-2956

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-2956/
Summaries are generated and may contain mistakes; the official description above is the record.