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

> Authenticated users can view all Jira projects without proper authorization checks, leading to unauthorized data disclosure.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Nov 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-r733-7pfp-9jx5

## What is CVE-2019-16909?

CVE-2019-16909 is a medium-severity missing authorization vulnerability in n/a, published on 1 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in the Infosysta "In-App & Desktop Notifications" app before 1.6.14_J8 for Jira. It is possible to obtain a list of all Jira projects (with authentication as a Jira user, but without authorization for specific projects) via the plugins/servlet/nfj/NotificationSettings URI.

Weakness: CWE-862 (Missing Authorization)

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

It affects 1 product.


Products: Infosysta In-App \& Desktop Notifications.

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

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

## Is CVE-2019-16909 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-16906](https://insights.sbomify.com/CVE-2019-16906/): Missing authorization in n/a (high 7.5)
- [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)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-16909 is a medium-severity missing authorization vulnerability in n/a, published on 1 Nov 2019. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-16909 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-16909/ (Markdown: https://insights.sbomify.com/CVE-2019-16909/index.md)
```

## Sources

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

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