{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-30948 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-30948 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-30948 is a medium-severity missing authorization vulnerability in com.palantir.comments:comments, published on 6 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-30948 and fix it if it is affected.\n\nWhat it is: CVE-2023-30948 is a medium-severity missing authorization vulnerability in com.palantir.comments:comments, published on 6 Jun 2023. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2023-30948 in the wild and no public exploit code.\n\nAffected product: com.palantir.comments:comments. 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-30948/ (Markdown: https://insights.sbomify.com/CVE-2023-30948/index.md)","id":"CVE-2023-30948","markdown":"https://insights.sbomify.com/CVE-2023-30948/index.md","name":"CVE-2023-30948","record":{"aliases":["GHSA-5c5c-cx8g-64x5"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Foundry Comments","requires_auth":"low_privilege","summary":"Authenticated users can access attachment content from arbitrary comments due to missing authorization checks in Foundry Comments.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Palantir","cpe":[{"product":"foundry_comments","vendor":"palantir"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-285","name":"Improper Authorization"}],"description":"A security defect in Foundry's Comments functionality resulted in the retrieval of attachments to comments not being gated by additional authorization checks. This could enable an authenticated user to inject a prior discovered attachment UUID into other arbitrary comments to discover it's content.\n\nThis defect was fixed in Foundry Comments 2.249.0, and a patch was rolled out to affected Foundry environments. No further intervention is required at this time.","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":"Retrieval of Attachments to Comments lacks Authorization","id":"CVE-2023-30948","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":"CVE-2023-30949","id":"CVE-2023-30949"},"packages":[],"prev":{"headline":"Issues notification metadata lacks authorization","id":"CVE-2023-30946"},"products":["com.palantir.comments:comments"],"published":"2023-06-06","related":[{"cvss_score":5.3,"headline":"IDOR in Foundry Comments allows retrieval of attachments","id":"CVE-2023-30956","kev_date_added":null,"published":"2023-07-10"}],"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":"2025-01-07","vendors":["Palantir"]},"summary":"Authenticated users can access attachment content from arbitrary comments due to missing authorization checks in Foundry Comments.","url":"https://insights.sbomify.com/CVE-2023-30948/"}