# CVE-2022-24108: Deserialization in n/a

> Remote attackers can achieve code execution and denial of service via unsafe deserialization in the Skyoftech So Listing Tabs module for OpenCart.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 17 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-4mw3-j4r4-8fq9

## What is CVE-2022-24108?

CVE-2022-24108 is a critical unsafe deserialization vulnerability in n/a, published on 17 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Skyoftech So Listing Tabs module 2.2.0 for OpenCart allows a remote attacker to inject a serialized PHP object via the setting parameter, potentially resulting in the ability to write to files on the server, cause DoS, and achieve remote code execution because of deserialization of untrusted data.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Skyoftech So Listing Tabs.

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

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

## Is CVE-2022-24108 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-24108 is a critical unsafe deserialization vulnerability in n/a, published on 17 May 2022. 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-24108 in the wild and no public exploit code.

Affected product: n/a. 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-24108/ (Markdown: https://insights.sbomify.com/CVE-2022-24108/index.md)
```

## Sources

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

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