# CVE-2022-4621: Panasonic Sanyo CCTV Network Camera

> Attackers can exploit CSRF vulnerabilities to perform administrative changes on Panasonic Sanyo CCTV Network Cameras.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2023
- **Updated:** 16 Jan 2025
- **Also known as:** GHSA-r3mf-hxp8-46h8

## What is CVE-2022-4621?

CVE-2022-4621 is a high-severity vulnerability in Panasonic Sanyo CCTV Network Camera, published on 17 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Panasonic Sanyo CCTV Network Cameras versions 1.02-05 and 2.03-0x are 
vulnerable to CSRFs that can be exploited to allow an attacker to 
perform changes with administrator level privileges.

Weakness: CWE-352 (Cross-Site Request Forgery)

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

It affects 5 products.


Products: Panasonic Vcc-Hd2100p Firmware, Panasonic Vcc-Hd3100p Firmware, Panasonic Vcc-Hd3300 Firmware, Panasonic Vcc-Hd3300p Firmware, Panasonic Vcc-Hd5600p Firmware.

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

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

## Is CVE-2022-4621 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-4621 is a high-severity vulnerability in Panasonic Sanyo CCTV Network Camera, published on 17 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-4621 in the wild and no public exploit code.

Affected product: Panasonic Sanyo CCTV Network Camera. 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-4621/ (Markdown: https://insights.sbomify.com/CVE-2022-4621/index.md)
```

## Sources

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

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