# CVE-2010-3719: Code injection in n/a

> Remote attackers with administrative access can execute arbitrary code via eval injection in the scheduling interface of Symantec IM Manager.

- **Severity:** High 8.5 (`AV:N/AC:M/Au:S/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Feb 2011
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-mr9w-cm2q-46cm

## What is CVE-2010-3719?

CVE-2010-3719 is a high-severity code injection vulnerability in n/a, published on 2 Feb 2011. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Eval injection vulnerability in IMAdminSchedTask.asp in the administrative interface for Symantec IM Manager 8.4.16 and earlier allows remote attackers to execute arbitrary code via unspecified parameters to the ScheduleTask method.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2010-3719?

It affects 1 product.


Products: Symantec Im Manager.

## How do I fix CVE-2010-3719?

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

## Is CVE-2010-3719 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-0553](https://insights.sbomify.com/CVE-2011-0553/): SQL injection in n/a (high 7.5)
- [CVE-2011-0554](https://insights.sbomify.com/CVE-2011-0554/): Code injection in n/a (high 7.5)
- [CVE-2010-0112](https://insights.sbomify.com/CVE-2010-0112/): SQL injection in n/a (high 7.5)
- [CVE-2011-0552](https://insights.sbomify.com/CVE-2011-0552/): Cross-site scripting in n/a (medium 4.3)
- [CVE-2009-3036](https://insights.sbomify.com/CVE-2009-3036/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-3719 and fix it if it is affected.

What it is: CVE-2010-3719 is a high-severity code injection vulnerability in n/a, published on 2 Feb 2011. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-3719 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-2010-3719/ (Markdown: https://insights.sbomify.com/CVE-2010-3719/index.md)
```

## Sources

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

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