# CVE-2011-1773: Auth bypass in n/a

> Local attackers can bypass VNC authentication on converted guests by connecting without a password due to missing password preservation.

- **Severity:** Medium 4.4 (`AV:L/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Feb 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-pv82-4539-jh36, RHSA-2011:1615

## What is CVE-2011-1773?

CVE-2011-1773 is a medium-severity authentication bypass vulnerability in Redhat Enterprise Linux, published on 8 Feb 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

virt-v2v before 0.8.4 does not preserve the VNC console password when converting a guest, which allows local users to bypass the intended VNC authentication by connecting without a password.

Weakness: CWE-255

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

It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `virt-v2v` | Red Hat:enterprise_linux:6::client | All versions | 0:0.8.3-5.el6 |
| `virt-v2v` | Red Hat:enterprise_linux:6::computenode | All versions | 0:0.8.3-5.el6 |
| `virt-v2v` | Red Hat:enterprise_linux:6::server | All versions | 0:0.8.3-5.el6 |
| `virt-v2v` | Red Hat:enterprise_linux:6::workstation | All versions | 0:0.8.3-5.el6 |

Products: Matthew Booth Virt-V2v, Redhat Enterprise Linux.

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

Upgrade to a fixed version.

## Is CVE-2011-1773 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2011-1773 is a medium-severity authentication bypass vulnerability in Redhat Enterprise Linux, published on 8 Feb 2014. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2011-1773 in the wild and no public exploit code.

Affected product: Redhat Enterprise Linux. 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-1773/ (Markdown: https://insights.sbomify.com/CVE-2011-1773/index.md)
```

## Sources

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

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