# CVE-2016-7442: Information disclosure in n/a

> Local administrators can read sensitive proxy user passwords from the anti-spam configuration settings in Sophos UTM.

- **Severity:** Medium 4.4 (`CVSS:3.0/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Oct 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-m7x6-w8mx-7jxr

## What is CVE-2016-7442?

CVE-2016-7442 is a medium-severity vulnerability in n/a, published on 3 Oct 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Frontend component in Sophos UTM with firmware 9.405-5 and earlier allows local administrators to obtain sensitive password information by reading the "value" field of the proxy user settings in "system settings / scan settings / anti spam" configuration tab.

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

## Which versions are affected by CVE-2016-7442?

It affects 1 product.


Products: Sophos Unified Threat Management Software.

## How do I fix CVE-2016-7442?

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

## Is CVE-2016-7442 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-5932](https://insights.sbomify.com/CVE-2013-5932/): Other in n/a (critical 10.0)
- [CVE-2016-2046](https://insights.sbomify.com/CVE-2016-2046/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2016-7397](https://insights.sbomify.com/CVE-2016-7397/): Information disclosure in n/a (medium 4.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-7442 and fix it if it is affected.

What it is: CVE-2016-7442 is a medium-severity vulnerability in n/a, published on 3 Oct 2016. 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-2016-7442 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-2016-7442/ (Markdown: https://insights.sbomify.com/CVE-2016-7442/index.md)
```

## Sources

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

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