# CVE-2013-0929: Other in n/a

> Remote attackers can execute arbitrary code via format string vulnerabilities in the Device Manager component of EMC AlphaStor.

- **Severity:** High 7.6 (`AV:N/AC:H/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Jan 2013
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-8qh3-332v-cx7g

## What is CVE-2013-0929?

CVE-2013-0929 is a high-severity vulnerability in n/a, published on 21 Jan 2013. It can be exploited over the network, with no action from the victim.

### Official description

Format string vulnerability in the _vsnsprintf function in rrobotd.exe in the Device Manager in EMC AlphaStor 4.0 before build 800 allows remote attackers to execute arbitrary code via format string specifiers in a command.

Weakness: CWE-134 (Use of Externally-Controlled Format String)

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

It affects 1 product.


Products: Emc Alphastor.

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

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

## Is CVE-2013-0929 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-0946](https://insights.sbomify.com/CVE-2013-0946/): Memory corruption in n/a (critical 9.3)
- [CVE-2013-0928](https://insights.sbomify.com/CVE-2013-0928/): Command injection in n/a (critical 9.3)
- [CVE-2013-0930](https://insights.sbomify.com/CVE-2013-0930/): Memory corruption in n/a (high 7.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2013-0929 is a high-severity vulnerability in n/a, published on 21 Jan 2013. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-0929 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-2013-0929/ (Markdown: https://insights.sbomify.com/CVE-2013-0929/index.md)
```

## Sources

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

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