{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-15260 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2020-15260 is a medium-severity vulnerability in pjsip pjproject, published on 10 Mar 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2020-15260 and fix it if it is affected.\n\nWhat it is: CVE-2020-15260 is a medium-severity vulnerability in pjsip pjproject, published on 10 Mar 2021. 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-2020-15260 in the wild and no public exploit code.\n\nAffected product: pjsip pjproject. 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-2020-15260/ (Markdown: https://insights.sbomify.com/CVE-2020-15260/index.md)","id":"CVE-2020-15260","markdown":"https://insights.sbomify.com/CVE-2020-15260/index.md","name":"CVE-2020-15260","record":{"aliases":["ALPINE-CVE-2020-15260","DEBIAN-CVE-2020-15260","GHSA-8hcp-hm38-mfph","UBUNTU-CVE-2020-15260"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"PJSIP multimedia library","requires_auth":"none","summary":"PJSIP reuses TLS connections based on IP address without verifying hostnames, enabling man-in-the-middle attacks via DNS spoofing.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pjsip","vendor":"teluu"}],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"},{"id":"CWE-297","name":"Improper Validation of Certificate with Host Mismatch"}],"description":"PJSIP is a free and open source multimedia communication library written in C language implementing standard based protocols such as SIP, SDP, RTP, STUN, TURN, and ICE. In version 2.10 and earlier, PJSIP transport can be reused if they have the same IP address + port + protocol. However, this is insufficient for secure transport since it lacks remote hostname authentication. Suppose we have created a TLS connection to `sip.foo.com`, which has an IP address `100.1.1.1`. If we want to create a TLS connection to another hostname, say `sip.bar.com`, which has the same IP address, then it will reuse that existing connection, even though `100.1.1.1` does not have certificate to authenticate as `sip.bar.com`. The vulnerability allows for an insecure interaction without user awareness. It affects users who need access to connections to different destinations that translate to the same address, and allows man-in-the-middle attack if attacker can route a connection to another destination such as in the case of DNS spoofing.","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":"Existing TLS connections can be reused without checking remote hostname","id":"CVE-2020-15260","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":0,"n_references":4,"next":{"headline":"Unquoted service path vulnerability on Veyon","id":"CVE-2020-15261"},"packages":[],"prev":{"headline":"CSRF in Auth0 ad-ldap-connector","id":"CVE-2020-15259"},"products":["pjproject"],"published":"2021-03-10","related":[{"cvss_score":9.8,"headline":"PJSIP has use-after-free vulnerability in SRTP media transport","id":"CVE-2023-38703","kev_date_added":null,"published":"2023-10-06"},{"cvss_score":9.1,"headline":"Media transport downgrade from the secure version (SRTP) to non-secure (RTP) in pjsip","id":"CVE-2022-39269","kev_date_added":null,"published":"2022-10-06"},{"cvss_score":8.8,"headline":"PJSIP: Stack overflow handling Service-Route headers in a registration response","id":"CVE-2026-57161","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":8.8,"headline":"PJSIP: Stack overflow parsing SDP a=crypto attributes","id":"CVE-2026-57162","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":8.8,"headline":"PJSIP: Stack overflow parsing a TLS peer certificate's SubjectAltName in GnuTLS backend","id":"CVE-2026-57163","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":8.4,"headline":"PJSIP: SDP parser out-of-bounds write in remote payload-type map maintenance","id":"CVE-2026-57159","kev_date_added":null,"published":"2026-09-04"},{"cvss_score":8.3,"headline":"PJSIP: Heap overflow in the HTTP client","id":"CVE-2026-57164","kev_date_added":null,"published":"2026-09-04"}],"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-04","vendors":["pjsip"]},"summary":"PJSIP reuses TLS connections based on IP address without verifying hostnames, enabling man-in-the-middle attacks via DNS spoofing.","url":"https://insights.sbomify.com/CVE-2020-15260/"}