# CVE-2019-11898: Unauthorized APE administration privileges can be achieved by reverse engineering one of the APE service tools.


- **Severity:** Critical 9.9 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 12 Sep 2019
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-v897-5qj5-2g64

## What is CVE-2019-11898?

CVE-2019-11898 is a critical vulnerability in Bosch Access Professional Edition, published on 12 Sep 2019. 

### Official description

Unauthorized APE administration privileges can be achieved by reverse engineering one of the APE service tools. The service tool is discontinued with Bosch Access Professional Edition (APE) 3.8.

Weakness: CWE-798 (Use of Hard-coded Credentials)

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

It affects 1 product.


Products: Bosch Access.

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

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

## Is CVE-2019-11898 being exploited?

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

## Other vulnerabilities in Bosch Access Professional Edition

- [CVE-2019-11899](https://insights.sbomify.com/CVE-2019-11899/): Missing authorization in Access Professional Edition (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11898 is a critical vulnerability in Bosch Access Professional Edition, published on 12 Sep 2019. 
Exploitation: There is no known exploitation of CVE-2019-11898 in the wild and no public exploit code.

Affected product: Bosch Access Professional Edition. 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-11898/ (Markdown: https://insights.sbomify.com/CVE-2019-11898/index.md)
```

## Sources

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

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