CVE-2017-1000021 XML external entity in n/a
High 8.8
Published
Updated
Check this codebase for CVE-2017-1000021 and fix it if it is affected.
What it is: CVE-2017-1000021 is a high-severity vulnerability in n/a, published on 13 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2017-1000021 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-2017-1000021/ (Markdown: https://insights.sbomify.com/CVE-2017-1000021/index.md)
Attackers can exploit XML External Entity vulnerabilities in LogicalDoc to read sensitive files or cause denial of service.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2017-1000021?
CVE-2017-1000021 is a high-severity vulnerability in n/a, published on 13 Jul 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
LogicalDoc Community Edition 7.5.3 and prior is vulnerable to XXE when indexing XML documents.
Weakness: CWE-611
Which versions are affected by CVE-2017-1000021?
It affects 1 product.
Products include Logicaldoc Logicaldoc.
How do I fix CVE-2017-1000021?
No fix has been published for CVE-2017-1000021 yet. Limit exposure of the affected software until one is available.
Is CVE-2017-1000021 being exploited?
There is no known exploitation of CVE-2017-1000021 in the wild and no public exploit code.
Other vulnerabilities in n/a
Sources
Also known as GHSA-4g7h-ghm5-8qmm.