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

> Remote attackers can execute arbitrary code via unsafe XStream deserialization in HTTL when configured with the XstreamCodec setting.

- **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:** 26 Nov 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jxhc-f56v-qm29

## What is CVE-2018-19530?

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

### Official description

HTTL (aka Hyper-Text Template Language) through 1.0.11 allows remote command execution because the decodeXml function uses XStream unsafely when configured with an xml.codec=httl.spi.codecs.XstreamCodec setting.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Httl Project Httl.

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

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

## Is CVE-2018-19530 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19531](https://insights.sbomify.com/CVE-2018-19531/): Code injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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