# CVE-2022-27969: Missing authorization in n/a

> Attackers can access a list of decoy users via an unauthenticated GET request, exposing sensitive internal configuration data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-wxgh-g8jm-vcx5

## What is CVE-2022-27969?

CVE-2022-27969 is a medium-severity missing authorization vulnerability in n/a, published on 8 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cynet 360 Web Portal before v4.5 was discovered to allow attackers to access a list of decoy users via a crafted GET request sent to /WebApp/DeceptionUser/GetAllDeceptionUsers.

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

It affects 1 product.


Products: Cynet Cynet 360.

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

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

## Is CVE-2022-27969 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-27967](https://insights.sbomify.com/CVE-2022-27967/): Information disclosure in n/a (medium 5.3)
- [CVE-2022-27968](https://insights.sbomify.com/CVE-2022-27968/): Missing authorization in n/a (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-27969 is a medium-severity missing authorization vulnerability in n/a, published on 8 Sep 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-27969 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-2022-27969/ (Markdown: https://insights.sbomify.com/CVE-2022-27969/index.md)
```

## Sources

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

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