# CVE-2017-16241: Missing authorization in n/a

> Remote attackers can execute door controller commands like locking or unlocking without authentication due to missing access controls.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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:** 10 Dec 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4gw8-qc3x-7gmv

## What is CVE-2017-16241?

CVE-2017-16241 is a high-severity missing authorization vulnerability in n/a, published on 10 Dec 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Incorrect access control in AMAG Symmetry Door Edge Network Controllers (EN-1DBC Boot App 23611 03.60 and STD App 23603 03.60; EN-2DBC Boot App 24451 01.00 and STD App 2461 01.00) enables remote attackers to execute door controller commands (e.g., lock, unlock, add ID card value) by sending unauthenticated requests to the affected devices via Serial over TCP/IP, as demonstrated by a Ud command.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

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

It affects 3 products.


Products: Amag En-1dbc Firmware, Amag En-2dbc Firmware, Amag Std Firmware.

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

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

## Is CVE-2017-16241 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2017-16241 is a high-severity missing authorization vulnerability in n/a, published on 10 Dec 2017. 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-2017-16241 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-16241/ (Markdown: https://insights.sbomify.com/CVE-2017-16241/index.md)
```

## Sources

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

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