CVE-2019-20191 XML external entity in n/a
High 7.5
Published
Updated
Check this codebase for CVE-2019-20191 and fix it if it is affected.
What it is: CVE-2019-20191 is a high-severity vulnerability in n/a, published on 16 Mar 2020. 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-20191 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-2019-20191/ (Markdown: https://insights.sbomify.com/CVE-2019-20191/index.md)
An attacker can exploit an XML External Entity vulnerability in Oxygen XML Editor to read arbitrary files from the local system.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2019-20191?
CVE-2019-20191 is a high-severity vulnerability in n/a, published on 16 Mar 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
Oxygen XML Editor 21.1.1 allows XXE to read any file.
Weakness: CWE-611
Which versions are affected by CVE-2019-20191?
It affects 3 products.
Products include Sync Oxygen Xml Author, Sync Oxygen Xml Developer, Sync Oxygen Xml Editor.
How do I fix CVE-2019-20191?
No fix has been published for CVE-2019-20191 yet. Limit exposure of the affected software until one is available.
Is CVE-2019-20191 being exploited?
There is no known exploitation of CVE-2019-20191 in the wild and no public exploit code.
Sources
Also known as GHSA-wrcc-xjp4-3f52.