# CVE-2019-5312: XML External Entity Reference in weixin-java-tools

> An XXE vulnerability in the weixin-java-tools library allows attackers to read sensitive files or cause denial of service via crafted XML.

- **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:** Yes
- **Published:** 4 Jan 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-h755-h99p-9ffv

## What is CVE-2019-5312?

CVE-2019-5312 is a critical vulnerability in n/a, published on 4 Jan 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in weixin-java-tools v3.3.0. There is an XXE vulnerability in the getXmlDoc method of the BaseWxPayResult.java file. NOTE: this issue exists because of an incomplete fix for CVE-2018-20318.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

## Which versions are affected by CVE-2019-5312?

2 open source packages ship an affected version, including com.github.binarywang:weixin-java-common. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.github.binarywang:weixin-java-common` | Maven | All versions | 3.3.2.B |
| `com.github.binarywang:weixin-java-common` | Maven | All versions | 3.3.2.B |

Products: Wxjava Project Wxjava.

## How do I fix CVE-2019-5312?

Upgrade com.github.binarywang:weixin-java-common to 3.3.2.B or later.

## Is CVE-2019-5312 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-20318](https://insights.sbomify.com/CVE-2018-20318/): XML external entity in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5312 and fix it if it is affected.

What it is: CVE-2019-5312 is a critical vulnerability in n/a, published on 4 Jan 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-2019-5312 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.github.binarywang:weixin-java-common (Maven): affected all versions; fixed in 3.3.2.B
- com.github.binarywang:weixin-java-common (Maven): affected all versions; fixed in 3.3.2.B

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-2019-5312/ (Markdown: https://insights.sbomify.com/CVE-2019-5312/index.md)
```

## Sources

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

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