# CVE-2013-6366: Code injection in n/a

> Remote authenticated administrators can execute arbitrary code via the Groovy script console in VMware Hyperic HQ.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-4pmc-q62v-29qw

## What is CVE-2013-6366?

CVE-2013-6366 is a medium-severity code injection vulnerability in n/a, published on 4 Nov 2013. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The Groovy script console in VMware Hyperic HQ 4.6.6 allows remote authenticated administrators to execute arbitrary code via a Runtime.getRuntime().exec call.

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

## Which versions are affected by CVE-2013-6366?

It affects 1 product.


Products: Vmware Hyperic Hq.

## How do I fix CVE-2013-6366?

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

## Is CVE-2013-6366 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6366 exists.

Public exploit code:

- VMware Hyperic HQ Groovy Script-Console - Java Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2009-2899](https://insights.sbomify.com/CVE-2009-2899/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-6366 and fix it if it is affected.

What it is: CVE-2013-6366 is a medium-severity code injection vulnerability in n/a, published on 4 Nov 2013. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2013-6366 exists.

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-2013-6366/ (Markdown: https://insights.sbomify.com/CVE-2013-6366/index.md)
```

## Sources

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

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