# CVE-2022-36444: Code injection in n/a

> Unauthenticated remote attackers can execute code or disrupt availability on Atos Unify OpenScape SBC, Branch, and BCF devices via the admin interface.

- **Severity:** High 8.6 (`CVSS:3.1/AC:L/AV:N/A:H/C:L/I:L/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-cpc9-mf28-84p2

## What is CVE-2022-36444?

CVE-2022-36444 is a high-severity code injection vulnerability in n/a, published on 25 Jul 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in Atos Unify OpenScape SBC 9 and 10 before 10R2.2.1, Atos Unify OpenScape Branch 9 and 10 before version 10R2.1.1, and Atos Unify OpenScape BCF 10 before 10R9.12.1. A remote code execution vulnerability may allow an unauthenticated attacker (with network access to the admin interface) to disrupt system availability or potentially compromise the confidentiality and integrity of the system.

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

It affects 3 products.


Products: Atos Unify Openscape Bcf, Atos Unify Openscape Branch, Atos Unify Openscape Session Border Controller.

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

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

## Is CVE-2022-36444 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-6269](https://insights.sbomify.com/CVE-2023-6269/): Command injection in OpenScape BCF (critical 10.0)
- [CVE-2023-30638](https://insights.sbomify.com/CVE-2023-30638/): Command injection in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-36444 is a high-severity code injection vulnerability in n/a, published on 25 Jul 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-36444 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-36444/ (Markdown: https://insights.sbomify.com/CVE-2022-36444/index.md)
```

## Sources

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

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