{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48057 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2025-48057 is a critical vulnerability in icinga2, published on 27 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48057 and fix it if it is affected.\n\nWhat it is: CVE-2025-48057 is a critical vulnerability in icinga2, published on 27 May 2025. 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-2025-48057 in the wild and no public exploit code.\n\nAffected product: icinga2. 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-2025-48057/ (Markdown: https://insights.sbomify.com/CVE-2025-48057/index.md)","id":"CVE-2025-48057","markdown":"https://insights.sbomify.com/CVE-2025-48057/index.md","name":"CVE-2025-48057","record":{"aliases":["DEBIAN-CVE-2025-48057","GHSA-7vcf-f5v9-3wr6","SUSE-SU-2025:02783-1","UBUNTU-CVE-2025-48057","openSUSE-SU-2025:15180-1"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["privilege_escalation","security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"Icinga monitoring system","requires_auth":"none","summary":"Attackers can bypass certificate validation to obtain valid certificates and impersonate trusted nodes in Icinga 2 when built with older OpenSSL versions.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"icinga","vendor":"icinga"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-296","name":"Improper Following of a Certificate's Chain of Trust"}],"description":"Icinga 2 is a monitoring system which checks the availability of network resources, notifies users of outages, and generates performance data for reporting. Prior to versions 2.12.12, 2.13.12, and 2.14.6, the VerifyCertificate() function can be tricked into incorrectly treating certificates as valid. This allows an attacker to send a malicious certificate request that is then treated as a renewal of an already existing certificate, resulting in the attacker obtaining a valid certificate that can be used to impersonate trusted nodes. This only occurs when Icinga 2 is built with OpenSSL older than version 1.1.0. This issue has been patched in versions 2.12.12, 2.13.12, and 2.14.6.","ecosystems":["SUSE:Linux Enterprise Module for HPC 12","openSUSE:Tumbleweed"],"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":"Icinga 2 certificate renewal might incorrectly renew an invalid certificate","id":"CVE-2025-48057","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":2,"n_references":6,"next":{"headline":"PowSyBl Core contains Polynomial REDoS’es","id":"CVE-2025-48058"},"packages":[{"ecosystem":"SUSE:Linux Enterprise Module for HPC 12","fixed":["2.8.2-3.11.2"],"introduced":["0"],"last_affected":[],"package":"icinga2","purl":"pkg:rpm/suse/icinga2\u0026distro=SUSE%20Linux%20Enterprise%20Module%20for%20HPC%2012","source":"SUSE-SU-2025:02783-1"},{"ecosystem":"openSUSE:Tumbleweed","fixed":["2.14.6-1.1"],"introduced":["0"],"last_affected":[],"package":"icinga2","purl":"pkg:rpm/opensuse/icinga2\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2025:15180-1"}],"prev":{"headline":"Hubble CLI vulnerable to character injection","id":"CVE-2025-48056"},"products":["icinga2"],"published":"2025-05-27","related":[{"cvss_score":9.1,"headline":"Security feature bypass in n/a","id":"CVE-2020-29663","kev_date_added":null,"published":"2020-12-15"},{"cvss_score":8.3,"headline":"Icinga Director configuration is susceptible to Cross-Site Request Forgery","id":"CVE-2024-24820","kev_date_added":null,"published":"2024-02-09"},{"cvss_score":8.1,"headline":"Information disclosure in n/a","id":"CVE-2018-6535","kev_date_added":null,"published":"2018-02-27"},{"cvss_score":7.8,"headline":"Path traversal in n/a","id":"CVE-2020-14004","kev_date_added":null,"published":"2020-06-12"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2018-6533","kev_date_added":null,"published":"2018-02-27"},{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2017-16882","kev_date_added":null,"published":"2017-11-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"SUSE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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":"total"},"state":"PUBLISHED","updated":"2025-05-27","vendors":["Icinga"]},"summary":"Attackers can bypass certificate validation to obtain valid certificates and impersonate trusted nodes in Icinga 2 when built with older OpenSSL versions.","url":"https://insights.sbomify.com/CVE-2025-48057/"}