{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2023-27585 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"CVE-2023-27585 is a high-severity memory corruption vulnerability in pjsip pjproject, published on 14 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-27585 and fix it if it is affected.\n\nWhat it is: CVE-2023-27585 is a high-severity memory corruption vulnerability in pjsip pjproject, published on 14 Mar 2023. 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-2023-27585 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-2023-27585/ (Markdown: https://insights.sbomify.com/CVE-2023-27585/index.md)","id":"CVE-2023-27585","markdown":"https://insights.sbomify.com/CVE-2023-27585/index.md","name":"CVE-2023-27585","record":{"aliases":["ALPINE-CVE-2023-27585","DEBIAN-CVE-2023-27585","DLA-3394-1","DSA-5438-1","DSA-5956-1","UBUNTU-CVE-2023-27585"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"PJSIP multimedia library","requires_auth":"none","summary":"A buffer overflow in the PJSIP DNS resolver allows attackers to execute arbitrary code or cause denial of service.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"pjsip","vendor":"teluu"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"},{"id":"CWE-120","name":"Buffer Copy without Checking Size of Input"}],"description":"PJSIP is a free and open source multimedia communication library written in C. A buffer overflow vulnerability in versions 2.13 and prior affects applications that use PJSIP DNS resolver. It doesn't affect PJSIP users who do not utilise PJSIP DNS resolver. This vulnerability is related to CVE-2022-24793. The difference is that this issue is in parsing the query record `parse_query()`, while the issue in CVE-2022-24793 is in `parse_rr()`. A patch is available as commit `d1c5e4d` in the `master` branch. A workaround is to disable DNS resolution in PJSIP config (by setting `nameserver_count` to zero) or use an external resolver implementation instead.","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":"Memory corruption in pjproject","id":"CVE-2023-27585","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2023"},"n_packages":0,"n_references":7,"next":{"headline":"CairoSVG improperly processes SVG files loaded from external resources","id":"CVE-2023-27586"},"packages":[],"prev":{"headline":"Dragonfly2 vulnerable to hard coded cyptographic key","id":"CVE-2023-27584"},"products":["pjproject"],"published":"2023-03-14","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-11-04","vendors":["pjsip"]},"summary":"A buffer overflow in the PJSIP DNS resolver allows attackers to execute arbitrary code or cause denial of service.","url":"https://insights.sbomify.com/CVE-2023-27585/"}