# CVE-2007-1462: Information disclosure in n/a

> Attackers can steal passwords by viewing the source of the Add System/Cluster page in Red Hat Conga's luci server.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 15 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-grcg-vmxx-7wq9

## What is CVE-2007-1462?

CVE-2007-1462 is a medium-severity vulnerability in n/a, published on 15 Mar 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The luci server component in conga preserves the password between page loads for the Add System/Cluster task flow by storing the password in the Value attribute of a password entry field, which allows attackers to steal the password by performing a "view source" or other operation to obtain the web page.  NOTE: there are limited circumstances under which such an attack is feasible.

## Which versions are affected by CVE-2007-1462?

It affects 1 product.


Products: Conga Conga.

## How do I fix CVE-2007-1462?

Apply the vendor's patch.

## Is CVE-2007-1462 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1462 and fix it if it is affected.

What it is: CVE-2007-1462 is a medium-severity vulnerability in n/a, published on 15 Mar 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-1462 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-2007-1462/ (Markdown: https://insights.sbomify.com/CVE-2007-1462/index.md)
```

## Sources

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

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