# CVE-2024-34598: Security feature bypass in GoodLock

> Local attackers can bypass security restrictions to install arbitrary applications via improper component export in Samsung GoodLock.

- **Severity:** High 7.7 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Sep 2025
- **Updated:** 4 Sep 2025
- **Also known as:** GHSA-cxrv-r3xh-g4p6

## What is CVE-2024-34598?

CVE-2024-34598 is a high-severity vulnerability in Samsung Mobile GoodLock, published on 4 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Improper export of component in GoodLock prior to version 2.2.04.95 allows local attackers to install arbitrary applications from Galaxy Store.

## Which versions are affected by CVE-2024-34598?

It affects 1 product.


Products: Samsung Good Lock.

## How do I fix CVE-2024-34598?

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

## Is CVE-2024-34598 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-34598 and fix it if it is affected.

What it is: CVE-2024-34598 is a high-severity vulnerability in Samsung Mobile GoodLock, published on 4 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-34598 in the wild and no public exploit code.

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

## Sources

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

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