# CVE-2022-27495: Missing authorization in NGINX Service Mesh

> Attackers can access control plane endpoints without authentication due to exposure on the cluster overlay network.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 May 2022
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qx4q-jhfj-788f

## What is CVE-2022-27495?

CVE-2022-27495 is a medium-severity missing authorization vulnerability in F5 NGINX Service Mesh, published on 5 May 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

On all versions 1.3.x (fixed in 1.4.0) NGINX Service Mesh control plane endpoints are exposed to the cluster overlay network. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2022-27495?

It affects 1 product.


Products: F5 Nginx Service Mesh.

## How do I fix CVE-2022-27495?

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

## Is CVE-2022-27495 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-27495 and fix it if it is affected.

What it is: CVE-2022-27495 is a medium-severity missing authorization vulnerability in F5 NGINX Service Mesh, published on 5 May 2022. 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-2022-27495 in the wild and no public exploit code.

Affected product: F5 NGINX Service Mesh. 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-2022-27495/ (Markdown: https://insights.sbomify.com/CVE-2022-27495/index.md)
```

## Sources

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

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