# CVE-2022-28743: Race condition in n/a

> Authenticated administrators can exploit a race condition in Foscam IP cameras to execute arbitrary code and gain root access to the underlying Linux system.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9wxq-wwqc-x64j

## What is CVE-2022-28743?

CVE-2022-28743 is a critical vulnerability in n/a, published on 21 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Time-of-check Time-of-use (TOCTOU) Race Condition vulerability in Foscam R2C IP camera running System FW <= 1.13.1.6, and Application FW <= 2.91.2.66, allows an authenticated remote attacker with administrator permissions to execute arbitrary remote code via a malicious firmware patch. The impact of this vulnerability is that the remote attacker could gain full remote access to the IP camera and the underlying Linux system with root permissions. With root access to the camera's Linux OS, an attacker could effectively change the code that is running, add backdoor access, or invade the privacy of the user by accessing the live camera stream.

Weakness: CWE-367 (Time-of-check Time-of-use (TOCTOU) Race Condition)

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

It affects 2 products.


Products: Foscam R2c Application Firmware, Foscam R2c System Firmware.

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

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

## Is CVE-2022-28743 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28743 is a critical vulnerability in n/a, published on 21 Apr 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-28743 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-28743/ (Markdown: https://insights.sbomify.com/CVE-2022-28743/index.md)
```

## Sources

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

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