# CVE-2013-6211: Information disclosure in n/a

> Remote attackers can obtain sensitive information or cause denial of service in HP StoreOnce backup systems via unspecified vectors.

- **Severity:** High 7.8 (`AV:N/AC:M/Au:N/C:P/I:N/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:** 29 Mar 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-538h-qg56-5hww

## What is CVE-2013-6211?

CVE-2013-6211 is a high-severity vulnerability in n/a, published on 29 Mar 2014. It can be exploited over the network, with no action from the victim.

### Official description

Unspecified vulnerability in HP StoreOnce Virtual Storage Appliance (VSA) before 3.7.2, StoreOnce 26xx and 4210 iSCSI Backup System before 3.9.0, StoreOnce 4210 FC Backup System before 3.9.0, and StoreOnce 4xxx Backup System before 3.9.0 allows remote attackers to obtain sensitive information or cause a denial of service via unknown vectors.

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

It affects 8 products.


Products: Hp Storeonce 2610 Iscsi Backup System, Hp Storeonce 2620 Iscsi Backup System, Hp Storeonce 4210 Fc Backup System, Hp Storeonce 4210 Iscsi Backup System, Hp Storeonce 4220 Backup System, Hp Storeonce 4420 Backup System, Hp Storeonce 4430 Backup System, Hp Storeonce Virtual Storage Appliance.

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

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

## Is CVE-2013-6211 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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