# CVE-2023-42552: Business logic in Firewall

> A third-party application can tamper with the Samsung Firewall database via implicit intent hijacking, compromising firewall settings.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Nov 2023
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-qcqr-cxwj-882p

## What is CVE-2023-42552?

CVE-2023-42552 is a medium-severity vulnerability in Samsung Mobile Firewall, published on 7 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Implicit intent hijacking vulnerability in Firewall application prior to versions 12.1.00.24 in Android 11, 13.1.00.16 in Android 12 and 14.1.00.7 in Android 13 allows 3rd party application to tamper the database of Firewall.

## Which versions are affected by CVE-2023-42552?

It affects 1 product.


Products: Samsung Firewall.

## How do I fix CVE-2023-42552?

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

## Is CVE-2023-42552 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-42552 and fix it if it is affected.

What it is: CVE-2023-42552 is a medium-severity vulnerability in Samsung Mobile Firewall, published on 7 Nov 2023. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-42552 in the wild and no public exploit code.

Affected product: Samsung Mobile Firewall. 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-42552/ (Markdown: https://insights.sbomify.com/CVE-2023-42552/index.md)
```

## Sources

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

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