# CVE-2022-47543: Auth bypass in n/a

> Attackers can bypass access controls on global objects in Siren Investigate, potentially reading unauthorized data.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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:** 5 Jan 2023
- **Updated:** 10 Apr 2025
- **Also known as:** GHSA-ghj4-5rg9-99rf

## What is CVE-2022-47543?

CVE-2022-47543 is a medium-severity authentication bypass vulnerability in n/a, published on 5 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Siren Investigate before 12.1.7. There is an ACL bypass on global objects.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Siren Investigate.

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

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

## Is CVE-2022-47543 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-35857](https://insights.sbomify.com/CVE-2023-35857/): Auth bypass in n/a (critical 9.8)
- [CVE-2022-47544](https://insights.sbomify.com/CVE-2022-47544/): Code injection in n/a (critical 9.8)
- [CVE-2021-36794](https://insights.sbomify.com/CVE-2021-36794/): Security feature bypass in n/a (critical 9.8)
- [CVE-2021-31216](https://insights.sbomify.com/CVE-2021-31216/): Server-side request forgery in n/a (high 8.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-47543 is a medium-severity authentication bypass vulnerability in n/a, published on 5 Jan 2023. 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-47543 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-47543/ (Markdown: https://insights.sbomify.com/CVE-2022-47543/index.md)
```

## Sources

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

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