# CVE-2018-11569: Deserialization in n/a

> An attacker can execute arbitrary code by exploiting unsafe deserialization in the Eventum issue tracker's list controller.

- **Severity:** Critical 9.8 (`CVSS:3.0/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:** 5 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3fvp-w97c-35v6

## What is CVE-2018-11569?

CVE-2018-11569 is a critical unsafe deserialization vulnerability in n/a, published on 5 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Controller/ListController.php in Eventum 3.5.0 is vulnerable to Deserialization of Untrusted Data. Fixed in version 3.5.2.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2018-11569?

It affects 1 product.


Products: Eventum Project Eventum.

## How do I fix CVE-2018-11569?

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

## Is CVE-2018-11569 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-12628](https://insights.sbomify.com/CVE-2018-12628/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2014-1632](https://insights.sbomify.com/CVE-2014-1632/): Code injection in n/a (high 8.1)
- [CVE-2014-1631](https://insights.sbomify.com/CVE-2014-1631/): Missing authorization in n/a (high 7.5)
- [CVE-2018-12622](https://insights.sbomify.com/CVE-2018-12622/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2018-12623](https://insights.sbomify.com/CVE-2018-12623/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-11569 and fix it if it is affected.

What it is: CVE-2018-11569 is a critical unsafe deserialization vulnerability in n/a, published on 5 Sep 2019. 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-2018-11569 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-2018-11569/ (Markdown: https://insights.sbomify.com/CVE-2018-11569/index.md)
```

## Sources

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

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