# CVE-2014-0347: Information disclosure in n/a

> Authenticated users can view cleartext passwords by modifying HTML input types in the Websense Unified Security Center settings interface.

- **Severity:** Low 3.5 (`AV:N/AC:M/Au:S/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:** No
- **Published:** 12 Apr 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-xmr6-rg25-v9gg

## What is CVE-2014-0347?

CVE-2014-0347 is a low-severity vulnerability in n/a, published on 12 Apr 2014. 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 Settings module in Websense Triton Unified Security Center 7.7.3 before Hotfix 31, Web Filter 7.7.3 before Hotfix 31, Web Security 7.7.3 before Hotfix 31, Web Security Gateway 7.7.3 before Hotfix 31, and Web Security Gateway Anywhere 7.7.3 before Hotfix 31 allows remote authenticated users to read cleartext passwords by replacing type="password" with type="text" in an INPUT element in the (1) Log Database or (2) User Directories component.

Weakness: CWE-255

## Which versions are affected by CVE-2014-0347?

It affects 5 products.


Products: Websense Triton Unified Security Center, Websense Triton Web Filter, Websense Triton Web Security, Websense Triton Web Security Gateway, Websense Triton Web Security Gateway Anywhere.

## How do I fix CVE-2014-0347?

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

## Is CVE-2014-0347 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-0347 and fix it if it is affected.

What it is: CVE-2014-0347 is a low-severity vulnerability in n/a, published on 12 Apr 2014. 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-2014-0347 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-2014-0347/ (Markdown: https://insights.sbomify.com/CVE-2014-0347/index.md)
```

## Sources

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

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