# CVE-2024-0302: fhs-opensource iparking vueLogin deserialization

> Remote attackers can achieve code execution via unsafe deserialization in the iparking web application's login endpoint.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2024
- **Updated:** 14 Nov 2024
- **Also known as:** GHSA-2rcq-rfc3-h2m5

## What is CVE-2024-0302?

CVE-2024-0302 is a medium-severity unsafe deserialization vulnerability in fhs-opensource iparking, published on 8 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, has been found in fhs-opensource iparking 1.5.22.RELEASE. This issue affects some unknown processing of the file /vueLogin. The manipulation leads to deserialization. The attack may be initiated remotely. The exploit has been disclosed to the public and may be used. The identifier VDB-249869 was assigned to this vulnerability.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Fhs-Opensource Iparking.

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

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

## Is CVE-2024-0302 being exploited?

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

## Other vulnerabilities in fhs-opensource iparking

- [CVE-2024-0301](https://insights.sbomify.com/CVE-2024-0301/): fhs-opensource iparking PayTempOrderAction.java getData sql injection (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-0302 is a medium-severity unsafe deserialization vulnerability in fhs-opensource iparking, published on 8 Jan 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-0302 in the wild and no public exploit code.

Affected product: fhs-opensource iparking. 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-0302/ (Markdown: https://insights.sbomify.com/CVE-2024-0302/index.md)
```

## Sources

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

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