# CVE-2016-1322: Auth bypass in n/a

> Remote attackers can bypass access restrictions in Cisco Spark to create arbitrary user accounts, leading to unauthorized access.

- **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:** 12 Feb 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r9hg-952w-h9jc

## What is CVE-2016-1322?

CVE-2016-1322 is a high-severity authentication bypass vulnerability in n/a, published on 12 Feb 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The REST interface in Cisco Spark 2015-07-04 allows remote attackers to bypass intended access restrictions and create arbitrary user accounts via unspecified web requests, aka Bug ID CSCuv72584.

Weakness: CWE-264

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

It affects 1 product.


Products: Cisco Spark.

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

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

## Is CVE-2016-1322 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-12269](https://insights.sbomify.com/CVE-2017-12269/): Cross-site scripting in Cisco Spark Messaging (medium 5.4)
- [CVE-2016-1324](https://insights.sbomify.com/CVE-2016-1324/): Denial of service in n/a (medium 5.3)
- [CVE-2016-1323](https://insights.sbomify.com/CVE-2016-1323/): Information disclosure in n/a (medium 4.3)
- [CVE-2015-6303](https://insights.sbomify.com/CVE-2015-6303/): Weak cryptography in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-1322 is a high-severity authentication bypass vulnerability in n/a, published on 12 Feb 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-1322 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-1322/ (Markdown: https://insights.sbomify.com/CVE-2016-1322/index.md)
```

## Sources

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

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