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

> Unauthenticated deserialization of Java objects in Xen Mobile allows remote code execution, though the vendor claims firewall restrictions mitigate this risk.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Oct 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-cwh4-297m-xrfv

## What is CVE-2018-18013?

CVE-2018-18013 is a high-severity unsafe deserialization vulnerability in n/a, published on 24 Oct 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

* Xen Mobile through 10.8.0 includes a service listening on port 5001 within its firewall that accepts unauthenticated input. If this service is supplied with raw serialised Java objects, it deserialises them back into Java objects in memory, giving rise to a remote code execution vulnerability.  NOTE: the vendor disputes that this is a vulnerability, stating it is "already mitigated by the internal firewall that limits access to configuration services to localhost.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

It affects 1 product.


Products: Citrix Xenmobile Server.

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

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

## Is CVE-2018-18013 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-8211](https://insights.sbomify.com/CVE-2020-8211/): SQL injection in Citrix XenMobile Server (critical 9.8)
- [CVE-2020-8212](https://insights.sbomify.com/CVE-2020-8212/): Missing authorization in Citrix XenMobile Server (critical 9.8)
- [CVE-2018-10648](https://insights.sbomify.com/CVE-2018-10648/): File upload in n/a (critical 9.8)
- [CVE-2018-10653](https://insights.sbomify.com/CVE-2018-10653/): XML external entity in n/a (critical 9.8)
- [CVE-2018-18571](https://insights.sbomify.com/CVE-2018-18571/): Auth bypass in n/a (critical 9.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-18013 is a high-severity unsafe deserialization vulnerability in n/a, published on 24 Oct 2018. 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-2018-18013 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-18013/ (Markdown: https://insights.sbomify.com/CVE-2018-18013/index.md)
```

## Sources

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

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