{"answers":{"affected":"It affects 4 products.","exploited":"There is no known exploitation of CVE-2023-31421 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2023-31421 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-31421 is a medium-severity vulnerability in Elastic APM Server, published on 26 Oct 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-31421 and fix it if it is affected.\n\nWhat it is: CVE-2023-31421 is a medium-severity vulnerability in Elastic APM Server, published on 26 Oct 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-31421 in the wild and no public exploit code.\n\nAffected product: Elastic APM Server. 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-31421/ (Markdown: https://insights.sbomify.com/CVE-2023-31421/index.md)","id":"CVE-2023-31421","markdown":"https://insights.sbomify.com/CVE-2023-31421/index.md","name":"CVE-2023-31421","record":{"aliases":["GHSA-4x46-8gg7-f9vx"],"analysis":{"component_type":"server_software","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Elastic observability stack","requires_auth":"none","summary":"Attackers can bypass TLS certificate validation when clients connect via IP address, enabling man-in-the-middle attacks against Elastic observability components.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"elastic","cpe":[{"product":"apm_server","vendor":"elastic"},{"product":"elastic_agent","vendor":"elastic"},{"product":"elastic_beats","vendor":"elastic"},{"product":"elastic_fleet_server","vendor":"elastic"}],"cvss":{"score":5.9,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"It was discovered that when acting as TLS clients, Beats, Elastic Agent, APM Server, and Fleet Server did not verify whether the server certificate is valid for the target IP address; however, certificate signature validation is still performed. More specifically, when the client is configured to connect to an IP address (instead of a hostname) it does not validate the server certificate's IP SAN values against that IP address and certificate validation fails, and therefore the connection is not blocked as expected.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Beats, Elastic Agent, APM Server, and Fleet Server Improper Certificate Validation issue","id":"CVE-2023-31421","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Kibana Insertion of Sensitive Information into Log File","id":"CVE-2023-31422"},"packages":[],"prev":{"headline":"Elasticsearch StackOverflow vulnerability","id":"CVE-2023-31419"},"products":["APM Server","Beats","Elastic Agent","Fleet Server"],"published":"2023-10-26","related":[{"cvss_score":5.7,"headline":"APM Server Insertion of Sensitive Information into Log File","id":"CVE-2024-37286","kev_date_added":null,"published":"2024-08-03"},{"cvss_score":5.7,"headline":"APM Server Insertion of Sensitive Information into Log File","id":"CVE-2024-23448","kev_date_added":null,"published":"2024-02-07"},{"cvss_score":4.9,"headline":"Improper Handling of Highly Compressed Data in APM Server Leading to Persistent Denial of Service","id":"CVE-2026-78594","kev_date_added":null,"published":"2026-09-02"}],"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-02","vendors":["Elastic"]},"summary":"Attackers can bypass TLS certificate validation when clients connect via IP address, enabling man-in-the-middle attacks against Elastic observability components.","url":"https://insights.sbomify.com/CVE-2023-31421/"}