# CVE-2011-0756: Hardcoded credentials in n/a

> Remote attackers can access the management console using hardcoded credentials to read security event data in Trustwave WebDefend Enterprise.

- **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:** 5 May 2011
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-m9jh-vhvg-rw99

## What is CVE-2011-0756?

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

### Official description

The application server in Trustwave WebDefend Enterprise before 5.0 uses hardcoded console credentials, which makes it easier for remote attackers to read security-event data by using the remote console GUI to connect to the management port.

Weakness: CWE-255

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

It affects 1 product.


Products: Trustwave Webdefend.

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

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

## Is CVE-2011-0756 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-1906](https://insights.sbomify.com/CVE-2011-1906/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2011-0756 is a medium-severity vulnerability in n/a, published on 5 May 2011. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-0756 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-2011-0756/ (Markdown: https://insights.sbomify.com/CVE-2011-0756/index.md)
```

## Sources

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

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