# CVE-2016-1452: Missing authorization in n/a

> Remote attackers can modify device configuration via SNMP if they know the read-write community string, affecting Cisco ASR 5000 devices.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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:** 15 Jul 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-54mh-qp5h-jfpv

## What is CVE-2016-1452?

CVE-2016-1452 is a medium-severity missing authorization vulnerability in n/a, published on 15 Jul 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Cisco ASR 5000 devices with software 18.3 through 20.0.0 allow remote attackers to make configuration changes over SNMP by leveraging knowledge of the read-write community, aka Bug ID CSCuz29526.

Weakness: CWE-254, CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2016-1452?

It affects 2 products.


Products: Cisco Asr 5000, Cisco Asr 5000 Software.

## How do I fix CVE-2016-1452?

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

## Is CVE-2016-1452 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-1452 and fix it if it is affected.

What it is: CVE-2016-1452 is a medium-severity missing authorization vulnerability in n/a, published on 15 Jul 2016. 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-2016-1452 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-2016-1452/ (Markdown: https://insights.sbomify.com/CVE-2016-1452/index.md)
```

## Sources

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

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