# CVE-2020-11589: Information disclosure in n/a

> Unauthenticated attackers can access sensitive information via insecure direct object references in CIPPlanner CIPAce.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-9vqw-64j6-rhmf

## What is CVE-2020-11589?

CVE-2020-11589 is a high-severity vulnerability in n/a, published on 6 Apr 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An Insecure Direct Object Reference issue was discovered in CIPPlanner CIPAce 9.1 Build 2019092801. An unauthenticated attacker can make a GET request to a certain URL and obtain information that should be provided to authenticated users only.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2020-11589?

It affects 1 product.


Products: Cipplanner Cipace.

## How do I fix CVE-2020-11589?

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

## Is CVE-2020-11589 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11586](https://insights.sbomify.com/CVE-2020-11586/): XML external entity in n/a (critical 9.8)
- [CVE-2020-11597](https://insights.sbomify.com/CVE-2020-11597/): SQL injection in n/a (critical 9.8)
- [CVE-2020-11598](https://insights.sbomify.com/CVE-2020-11598/): File upload in n/a (critical 9.8)
- [CVE-2024-50619](https://insights.sbomify.com/CVE-2024-50619/): Privilege escalation in n/a (high 8.8)
- [CVE-2024-50620](https://insights.sbomify.com/CVE-2024-50620/): File upload in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-11589 and fix it if it is affected.

What it is: CVE-2020-11589 is a high-severity vulnerability in n/a, published on 6 Apr 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-2020-11589 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-2020-11589/ (Markdown: https://insights.sbomify.com/CVE-2020-11589/index.md)
```

## Sources

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

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