{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-8361 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-8361 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-8361 is a critical missing authorization vulnerability in n/a, published on 8 Feb 2016. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-8361 and fix it if it is affected.\n\nWhat it is: CVE-2015-8361 is a critical missing authorization vulnerability in n/a, published on 8 Feb 2016. 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-2015-8361 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-2015-8361/ (Markdown: https://insights.sbomify.com/CVE-2015-8361/index.md)","id":"CVE-2015-8361","markdown":"https://insights.sbomify.com/CVE-2015-8361/index.md","name":"CVE-2015-8361","record":{"aliases":["GHSA-p635-3wgg-xwf4"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Atlassian Bamboo","requires_auth":"none","summary":"Remote attackers can access sensitive information, modify settings, or manage build agents in Atlassian Bamboo due to missing authentication on JMS services.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"bamboo","vendor":"atlassian"}],"cvss":{"score":9.1,"severity":"critical","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"Multiple unspecified services in Atlassian Bamboo before 5.9.9 and 5.10.x before 5.10.0 do not require authentication, which allows remote attackers to obtain sensitive information, modify settings, or manage build agents via unknown vectors involving the JMS port.","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-2015-8361","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2015"},"n_packages":0,"n_references":4,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2015-8362"},"packages":[],"prev":{"headline":"Deserialization in n/a","id":"CVE-2015-8360"},"products":["n/a"],"published":"2016-02-08","related":[{"cvss_score":9.3,"headline":"Atlassian Multiple Products Files or Directories Accessible to External Parties","id":"CVE-2026-21589","kev_date_added":"2026-10-15","published":"2026-10-05"},{"cvss_score":9.8,"headline":"Auth bypass in Bamboo Data Center","id":"CVE-2022-26136","kev_date_added":null,"published":"2022-07-20"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2016-5229","kev_date_added":null,"published":"2016-08-02"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2014-9757","kev_date_added":null,"published":"2016-02-08"},{"cvss_score":9.8,"headline":"Deserialization in n/a","id":"CVE-2015-8360","kev_date_added":null,"published":"2016-02-08"},{"cvss_score":9.6,"headline":"Code injection in Bamboo","id":"CVE-2017-14589","kev_date_added":null,"published":"2017-12-13"},{"cvss_score":9.4,"headline":"Command injection in Bamboo Data Center","id":"CVE-2026-21571","kev_date_added":null,"published":"2026-04-21"}],"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-06","vendors":["n/a"]},"summary":"Remote attackers can access sensitive information, modify settings, or manage build agents in Atlassian Bamboo due to missing authentication on JMS services.","url":"https://insights.sbomify.com/CVE-2015-8361/"}