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

> Attackers can read and consume other users' notifications without authentication by manipulating the username parameter in the Jira notification plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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:** 31 Oct 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-mq4x-26c5-hg9p

## What is CVE-2019-16906?

CVE-2019-16906 is a high-severity missing authorization vulnerability in n/a, published on 31 Oct 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in the Infosysta "In-App & Desktop Notifications" app 1.6.13_J8 for Jira. By using plugins/servlet/nfj/PushNotification?username= with a modified username, a different user's notifications can be read without authentication/authorization. These notifications are then no longer displayed to the normal user.

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

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

It affects 1 product.


Products: Infosysta In-App \& Desktop Notifications.

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

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

## Is CVE-2019-16906 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16908](https://insights.sbomify.com/CVE-2019-16908/): Missing authorization in n/a (medium 5.3)
- [CVE-2019-16907](https://insights.sbomify.com/CVE-2019-16907/): Information disclosure in n/a (medium 5.3)
- [CVE-2019-16909](https://insights.sbomify.com/CVE-2019-16909/): Missing authorization in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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