# CVE-2019-9657: Missing authorization in n/a

> Attackers can bypass access controls on Alarm.com cameras due to improper protection of VPN certificates, potentially compromising device security.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/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:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Jul 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-pxgp-xp3x-chh5

## What is CVE-2019-9657?

CVE-2019-9657 is a high-severity missing authorization vulnerability in n/a, published on 11 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Alarm.com ADC-V522IR 0100b9 devices have Incorrect Access Control, a different issue than CVE-2018-19588. This occurs because of incorrect protection of VPN certificates (used for initiating a VPN session to the Alarm.com infrastructure) on the local camera device.

Weakness: CWE-522 (Insufficiently Protected Credentials)

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

It affects 1 product.


Products: Alarm Adc-V522ir Firmware.

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

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

## Is CVE-2019-9657 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-19588](https://insights.sbomify.com/CVE-2018-19588/): Missing authorization in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-9657 is a high-severity missing authorization vulnerability in n/a, published on 11 Jul 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-9657 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-9657/ (Markdown: https://insights.sbomify.com/CVE-2019-9657/index.md)
```

## Sources

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

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