# CVE-2023-45672: Frigate unsafe deserialization in `load_config_with_no_duplicates` of `frigate/util/builtin.py` > An unsafe deserialization flaw in Frigate allows remote code execution if an authenticated user is tricked into visiting a malicious link. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** A user has to click or open something - **Fix available:** No - **Published:** 30 Oct 2023 - **Updated:** 2 Aug 2024 - **Also known as:** GHSA-qp3h-4q62-p428 ## What is CVE-2023-45672? CVE-2023-45672 is a high-severity unsafe deserialization vulnerability in blakeblackshear frigate, published on 30 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. ### Official description Frigate is an open source network video recorder. Prior to version 0.13.0 Beta 3, an unsafe deserialization vulnerability was identified in the endpoints used to save configurations for Frigate. This can lead to unauthenticated remote code execution. This can be performed through the UI at `/config` or through a direct call to `/api/config/save`. Exploiting this vulnerability requires the attacker to both know very specific information about a user's Frigate server and requires an authenticated user to be tricked into clicking a specially crafted link to their Frigate instance. This vulnerability could exploited by an attacker under the following circumstances: Frigate publicly exposed to the internet (even with authentication); attacker knows the address of a user's Frigate instance; attacker crafts a specialized page which links to the user's Frigate instance; attacker finds a way to get an authenticated user to visit their specialized page and click the button/link. Input is initially accepted through `http.py`. The user-provided input is then parsed and loaded by `load_config_with_no_duplicates`. However, `load_config_with_no_duplicates` does not sanitize this input by merit of using `yaml.loader.Loader` which can instantiate custom constructors. A provided payload will be executed directly at `frigate/util/builtin.py:110`. This issue may lead to pre-authenticated Remote Code Execution. Version 0.13.0 Beta 3 contains a patch. Weakness: CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2023-45672? It affects 1 product. Products: Frigate Frigate. ## How do I fix CVE-2023-45672? No fix has been published for CVE-2023-45672 yet. Limit exposure of the affected software until one is available. ## Is CVE-2023-45672 being exploited? There is no known exploitation of CVE-2023-45672 in the wild and no public exploit code. ## Other vulnerabilities in blakeblackshear frigate - [CVE-2026-25643](https://insights.sbomify.com/CVE-2026-25643/): Frigate Affected by Authenticated Remote Command Execution (RCE) and Container Escape (critical 9.1) - [CVE-2026-33124](https://insights.sbomify.com/CVE-2026-33124/): Frigate has insecure password change functionality (high 8.6) - [CVE-2023-45670](https://insights.sbomify.com/CVE-2023-45670/): Frigate cross-site request forgery in `config_save` and `config_set` request handlers (high 7.5) - [CVE-2026-33125](https://insights.sbomify.com/CVE-2026-33125/): Frigate Broken Access Control: Users assigned the viewer role can delete admin and other low-privileged accounts (high 7.1) - [CVE-2026-33469](https://insights.sbomify.com/CVE-2026-33469/): Authenticated Frigate users can read the full unredacted configuration via `/api/config/raw (medium 6.5) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-45672 and fix it if it is affected. What it is: CVE-2023-45672 is a high-severity unsafe deserialization vulnerability in blakeblackshear frigate, published on 30 Oct 2023. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link. Exploitation: There is no known exploitation of CVE-2023-45672 in the wild and no public exploit code. Affected product: blakeblackshear frigate. 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-2023-45672/ (Markdown: https://insights.sbomify.com/CVE-2023-45672/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-45672 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-45672 - OSV: https://osv.dev/vulnerability/CVE-2023-45672 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-45672/ Summaries are generated and may contain mistakes; the official description above is the record.