# CVE-2021-32007: Missing security header: Referrer-Policy URL

> Missing Referrer-Policy header in Secomea GateManager allows potential information leakage to remote servers.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/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:** 13 Dec 2024
- **Updated:** 23 Dec 2024
- **Also known as:** GHSA-4gfm-4g53-grgf

## What is CVE-2021-32007?

CVE-2021-32007 is a low-severity vulnerability in Secomea GateManager, published on 13 Dec 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

This issue affects:
Secomea GateManager
Version 9.5 and all prior versions.
Protection Mechanism Failure vulnerability in web server of Secomea GateManager to potentially leak information to remote servers.

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

## Which versions are affected by CVE-2021-32007?


## How do I fix CVE-2021-32007?

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

## Is CVE-2021-32007 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-32007 and fix it if it is affected.

What it is: CVE-2021-32007 is a low-severity vulnerability in Secomea GateManager, published on 13 Dec 2024. 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-2021-32007 in the wild and no public exploit code.

Affected product: Secomea GateManager. 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-2021-32007/ (Markdown: https://insights.sbomify.com/CVE-2021-32007/index.md)
```

## Sources

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

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