{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-30946 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-30946 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-30946 is a low-severity missing authorization vulnerability in com.palantir.issues:issues, published on 29 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2023-30946 and fix it if it is affected.\n\nWhat it is: CVE-2023-30946 is a low-severity missing authorization vulnerability in com.palantir.issues:issues, published on 29 Jun 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2023-30946 in the wild and no public exploit code.\n\nAffected product: com.palantir.issues:issues. 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-2023-30946/ (Markdown: https://insights.sbomify.com/CVE-2023-30946/index.md)","id":"CVE-2023-30946","markdown":"https://insights.sbomify.com/CVE-2023-30946/index.md","name":"CVE-2023-30946","record":{"aliases":["GHSA-63fq-r3mp-fpcf"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Foundry Issues","requires_auth":"low_privilege","summary":"Attackers can access sensitive issue metadata via the Notification API without proper authorization checks, exposing internal identifiers and titles.","user_interaction":"required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Palantir","cpe":[{"product":"foundry_issues","vendor":"palantir"}],"cvss":{"score":3.5,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-420","name":"Unprotected Alternate Channel"},{"id":"CWE-288","name":"Authentication Bypass Using an Alternate Path or Channel"}],"description":"A security defect was identified in Foundry Issues. If a user was added to an issue on a resource that they did not have access to and consequently could not see, they could query Foundry's Notification API and receive metadata about the issue including the RID of the issue, severity, internal UUID of the author, and the user-defined title of the issue.","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":"Issues notification metadata lacks authorization","id":"CVE-2023-30946","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2023"},"n_packages":0,"n_references":1,"next":{"headline":"Retrieval of Attachments to Comments lacks Authorization","id":"CVE-2023-30948"},"packages":[],"prev":{"headline":"CVE-2023-30945","id":"CVE-2023-30945"},"products":["com.palantir.issues:issues"],"published":"2023-06-29","related":[{"cvss_score":5.5,"headline":"The Foundry Issues service was found to be logging in a manner that captured session tokens.","id":"CVE-2022-27888","kev_date_added":null,"published":"2022-04-26"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-10-28","vendors":["Palantir"]},"summary":"Attackers can access sensitive issue metadata via the Notification API without proper authorization checks, exposing internal identifiers and titles.","url":"https://insights.sbomify.com/CVE-2023-30946/"}