{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2017-14603 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2017-14603 is a high-severity vulnerability in Digium Asterisk, published on 9 Oct 2017. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2017-14603 and fix it if it is affected.\n\nWhat it is: CVE-2017-14603 is a high-severity vulnerability in Digium Asterisk, published on 9 Oct 2017. 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-2017-14603 in the wild and no public exploit code.\n\nAffected product: Digium Asterisk. 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-2017-14603/ (Markdown: https://insights.sbomify.com/CVE-2017-14603/index.md)","id":"CVE-2017-14603","markdown":"https://insights.sbomify.com/CVE-2017-14603/index.md","name":"CVE-2017-14603","record":{"aliases":["DEBIAN-CVE-2017-14603","DSA-3990-1","GHSA-p6hc-c268-h4wx","UBUNTU-CVE-2017-14603"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","other"],"network_reachable":"yes","non_default_config":true,"product_category":"Asterisk PBX","requires_auth":"none","summary":"Insufficient RTCP validation in Asterisk allows reading stale buffer contents and potentially redirecting RTCP reports when specific NAT options are enabled.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"asterisk","vendor":"digium"},{"product":"certified_asterisk","vendor":"digium"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/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":"In Asterisk 11.x before 11.25.3, 13.x before 13.17.2, and 14.x before 14.6.2 and Certified Asterisk 11.x before 11.6-cert18 and 13.x before 13.13-cert6, insufficient RTCP packet validation could allow reading stale buffer contents and when combined with the \"nat\" and \"symmetric_rtp\" options allow redirecting where Asterisk sends the next RTCP report.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Information disclosure in n/a","id":"CVE-2017-14603","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"digium:asterisk","products":["digium:asterisk","digium:certified_asterisk"],"type":"information_disclosure","year":"2017"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2017-14604"},"packages":[],"prev":{"headline":"Auth bypass in n/a","id":"CVE-2017-14602"},"products":["n/a"],"published":"2017-10-09","related":[{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2017-14100","kev_date_added":null,"published":"2017-09-02"},{"cvss_score":9,"headline":"Privilege escalation in n/a","id":"CVE-2014-8418","kev_date_added":null,"published":"2014-11-24"},{"cvss_score":9,"headline":"Missing authorization in n/a","id":"CVE-2011-1599","kev_date_added":null,"published":"2011-04-27"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-16671","kev_date_added":null,"published":"2017-11-09"},{"cvss_score":8.8,"headline":"Memory corruption in n/a","id":"CVE-2017-7617","kev_date_added":null,"published":"2017-04-10"},{"cvss_score":7.8,"headline":"Denial of service in n/a","id":"CVE-2009-2726","kev_date_added":null,"published":"2009-08-12"},{"cvss_score":7.8,"headline":"Null dereference in n/a","id":"CVE-2007-1306","kev_date_added":null,"published":"2007-03-07"}],"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-05","vendors":["n/a"]},"summary":"Insufficient RTCP validation in Asterisk allows reading stale buffer contents and potentially redirecting RTCP reports when specific NAT options are enabled.","url":"https://insights.sbomify.com/CVE-2017-14603/"}