{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2013-6970 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2013-6970 yet. Limit exposure of the affected software until one is available.","what":"CVE-2013-6970 is a medium-severity vulnerability in n/a, published on 14 Dec 2013. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2013-6970 and fix it if it is affected.\n\nWhat it is: CVE-2013-6970 is a medium-severity vulnerability in n/a, published on 14 Dec 2013. 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-2013-6970 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-2013-6970/ (Markdown: https://insights.sbomify.com/CVE-2013-6970/index.md)","id":"CVE-2013-6970","markdown":"https://insights.sbomify.com/CVE-2013-6970/index.md","name":"CVE-2013-6970","record":{"aliases":["GHSA-p68h-cww3-2rx9"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Cisco WebEx Meeting Center","requires_auth":"none","summary":"Remote attackers can obtain sensitive information by reading verbose error messages in Cisco WebEx Meeting Center server responses.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[{"product":"webex_meeting_center","vendor":"cisco"}],"cvss":{"score":5,"severity":"medium","source":"nvd","vector":"AV:N/AC:L/Au:N/C:P/I:N/A:N","version":"2.0"},"cwes":[{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Cisco WebEx Meeting Center allows remote attackers to obtain sensitive information by reading verbose error messages within server responses, aka Bug ID CSCul35928.","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":"Information disclosure in n/a","id":"CVE-2013-6970","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2013"},"n_packages":0,"n_references":4,"next":{"headline":"Open redirect in n/a","id":"CVE-2013-6971"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2013-6969"},"products":["n/a"],"published":"2013-12-14","related":[{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2016-1410","kev_date_added":null,"published":"2016-05-28"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2015-4208","kev_date_added":null,"published":"2015-06-24"},{"cvss_score":6.8,"headline":"Memory corruption in n/a","id":"CVE-2010-3270","kev_date_added":null,"published":"2011-02-02"},{"cvss_score":6.5,"headline":"Memory corruption in Cisco WebEx Network Recording Player","id":"CVE-2017-12359","kev_date_added":null,"published":"2017-11-30"},{"cvss_score":6.4,"headline":"Missing authorization in n/a","id":"CVE-2015-4209","kev_date_added":null,"published":"2015-06-23"},{"cvss_score":6.1,"headline":"Cross-site scripting in Cisco WebEx Meeting Center","id":"CVE-2017-12366","kev_date_added":null,"published":"2017-11-30"},{"cvss_score":6.1,"headline":"Cross-site scripting in Cisco WebEx Meeting Center","id":"CVE-2017-12298","kev_date_added":null,"published":"2017-10-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)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-06","vendors":["n/a"]},"summary":"Remote attackers can obtain sensitive information by reading verbose error messages in Cisco WebEx Meeting Center server responses.","url":"https://insights.sbomify.com/CVE-2013-6970/"}