{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16906 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16906 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2019-16906 and fix it if it is affected.\n\nWhat 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.\nExploitation: There is no known exploitation of CVE-2019-16906 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2019-16906/ (Markdown: https://insights.sbomify.com/CVE-2019-16906/index.md)","id":"CVE-2019-16906","markdown":"https://insights.sbomify.com/CVE-2019-16906/index.md","name":"CVE-2019-16906","record":{"aliases":["GHSA-mq4x-26c5-hg9p"],"analysis":{"component_type":"cms_plugin","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Jira notification plugin","requires_auth":"none","summary":"Attackers can read and consume other users' notifications without authentication by manipulating the username parameter in the Jira notification plugin.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"in-app_\\\u0026_desktop_notifications","vendor":"infosysta"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"An issue was discovered in the Infosysta \"In-App \u0026 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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Missing authorization in n/a","id":"CVE-2019-16906","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-16907"},"packages":[],"prev":{"headline":"Integer overflow in n/a","id":"CVE-2019-16905"},"products":["n/a"],"published":"2019-10-31","related":[{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2019-16908","kev_date_added":null,"published":"2019-11-01"},{"cvss_score":5.3,"headline":"Information disclosure in n/a","id":"CVE-2019-16907","kev_date_added":null,"published":"2019-10-31"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2019-16909","kev_date_added":null,"published":"2019-11-01"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can read and consume other users' notifications without authentication by manipulating the username parameter in the Jira notification plugin.","url":"https://insights.sbomify.com/CVE-2019-16906/"}