# CVE-2011-3011: Information disclosure in n/a

> Remote attackers can obtain credentials and execute arbitrary commands due to improper session handling in CA ARCserve D2D.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Aug 2011
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-4xp4-9qmj-752r

## What is CVE-2011-3011?

CVE-2011-3011 is a medium-severity vulnerability in n/a, published on 15 Aug 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BaseServiceImpl.class in CA ARCserve D2D r15 does not properly handle sessions, which allows remote attackers to obtain credentials, and consequently execute arbitrary commands, via unspecified vectors.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2011-3011?

It affects 1 product.


Products: Ca Arcserve D2d.

## How do I fix CVE-2011-3011?

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

## Is CVE-2011-3011 being exploited?

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

Public exploit code:

- CA Arcserve D2D - GWT RPC Credential Information Disclosure (Metasploit) (exploitdb)
- CA Arcserve D2D GWT RPC Credential Information Disclosure (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2011-3011 and fix it if it is affected.

What it is: CVE-2011-3011 is a medium-severity vulnerability in n/a, published on 15 Aug 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2011-3011 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-2011-3011/ (Markdown: https://insights.sbomify.com/CVE-2011-3011/index.md)
```

## Sources

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

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