{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2015-4682 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2015-4682 yet. Limit exposure of the affected software until one is available.","what":"CVE-2015-4682 is a medium-severity vulnerability in n/a, published on 19 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2015-4682 and fix it if it is affected.\n\nWhat it is: CVE-2015-4682 is a medium-severity vulnerability in n/a, published on 19 Sep 2017. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2015-4682 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-4682/ (Markdown: https://insights.sbomify.com/CVE-2015-4682/index.md)","id":"CVE-2015-4682","markdown":"https://insights.sbomify.com/CVE-2015-4682/index.md","name":"CVE-2015-4682","record":{"aliases":["GHSA-4qh5-p5x2-2wcj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Polycom RPRM","requires_auth":"low_privilege","summary":"Authenticated attackers can obtain the installation path via a specific HTTP POST request, exposing internal directory structure information.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"realpresence_resource_manager","vendor":"polycom"}],"cvss":{"score":6.5,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Polycom RealPresence Resource Manager (aka RPRM) before 8.4 allows remote authenticated users to obtain the installation path via an HTTP POST request to PlcmRmWeb/JConfigManager.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2015-06-30","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2015-06-30","kind":"exploitdb","ref":"37449","stars":null,"title":"Polycom RealPresence Resource Manager \u003c 8.4 - Multiple Vulnerabilities"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2015-4682","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2015"},"n_packages":0,"n_references":6,"next":{"headline":"Information disclosure in n/a","id":"CVE-2015-4683"},"packages":[],"prev":{"headline":"Hardcoded credentials in n/a","id":"CVE-2015-4681"},"products":["n/a"],"published":"2017-09-19","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2015-4683","kev_date_added":null,"published":"2017-09-19"},{"cvss_score":7.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2015-4681","kev_date_added":null,"published":"2017-09-19"},{"cvss_score":7,"headline":"Privilege escalation in n/a","id":"CVE-2015-4685","kev_date_added":null,"published":"2017-09-19"},{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2015-4684","kev_date_added":null,"published":"2017-09-19"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Authenticated attackers can obtain the installation path via a specific HTTP POST request, exposing internal directory structure information.","url":"https://insights.sbomify.com/CVE-2015-4682/"}