# CVE-2019-11857: ALEOS AceManager Information Disclosure

> Attackers can disclose sensitive system information via AceManager due to lack of input sanitization in Sierra Wireless ALEOS devices.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Aug 2020
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-6p98-gw22-pp6c

## What is CVE-2019-11857?

CVE-2019-11857 is a critical vulnerability in n/a, published on 21 Aug 2020. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Lack of input sanitization in AceManager of ALEOS before 4.12.0, 4.9.5 and 4.4.9 allows disclosure of sensitive system information.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Sierrawireless Aleos.

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

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

## Is CVE-2019-11857 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-4063](https://insights.sbomify.com/CVE-2018-4063/): Sierra Wireless AirLink ALEOS Unrestricted Upload of File with Dangerous Type (high 8.8, exploited in the wild)
- [CVE-2015-2897](https://insights.sbomify.com/CVE-2015-2897/): Hardcoded credentials in n/a (critical 10.0)
- [CVE-2019-11851](https://insights.sbomify.com/CVE-2019-11851/): Memory corruption in n/a (critical 9.8)
- [CVE-2018-10251](https://insights.sbomify.com/CVE-2018-10251/): Missing authorization in n/a (critical 9.8)
- [CVE-2022-46649](https://insights.sbomify.com/CVE-2022-46649/): Command injection in ALEOS (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-11857 is a critical vulnerability in n/a, published on 21 Aug 2020. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11857 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-11857/ (Markdown: https://insights.sbomify.com/CVE-2019-11857/index.md)
```

## Sources

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

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