# CVE-2017-1000022: Privilege escalation in n/a

> Attackers can escalate privileges in LogicalDoc Community Edition due to incorrect access control, requiring an upgrade to secure the system.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-6352-7w6q-26g4

## What is CVE-2017-1000022?

CVE-2017-1000022 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 contain an Incorrect access control which could leave to privilege escalation.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2017-1000022?

It affects 1 product.


Products: Logicaldoc Logicaldoc.

## How do I fix CVE-2017-1000022?

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

## Is CVE-2017-1000022 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-9423](https://insights.sbomify.com/CVE-2020-9423/): File upload in n/a (critical 9.8)
- [CVE-2020-13542](https://insights.sbomify.com/CVE-2020-13542/): Privilege escalation in LogicalDoc (critical 9.3)
- [CVE-2017-1000021](https://insights.sbomify.com/CVE-2017-1000021/): XML external entity in n/a (high 8.8)
- [CVE-2024-54449](https://insights.sbomify.com/CVE-2024-54449/): Remote Code Execution (RCE) via Arbitrary File Write In Document API (high 8.7)
- [CVE-2024-54448](https://insights.sbomify.com/CVE-2024-54448/): Remote Code Execution (RCE) via Automation Scripting (high 8.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-1000022 and fix it if it is affected.

What it is: CVE-2017-1000022 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-1000022 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-1000022/ (Markdown: https://insights.sbomify.com/CVE-2017-1000022/index.md)
```

## Sources

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

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