{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-43918 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-43918 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-43918 is a medium-severity vulnerability in SSL.com, published on 19 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-43918 and fix it if it is affected.\n\nWhat it is: CVE-2025-43918 is a medium-severity vulnerability in SSL.com, published on 19 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-43918 in the wild and no public exploit code.\n\nAffected product: SSL.com. 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-43918/ (Markdown: https://insights.sbomify.com/CVE-2025-43918/index.md)","id":"CVE-2025-43918","markdown":"https://insights.sbomify.com/CVE-2025-43918/index.md","name":"CVE-2025-43918","record":{"aliases":["GHSA-6294-g9w5-7vm5"],"analysis":{"component_type":"cloud_service","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"SSL.com certificate authority","requires_auth":"low_privilege","summary":"Attackers can obtain trusted TLS certificates for domains they do not control by exploiting a flaw in SSL.com's domain validation logic.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":6.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-348","name":"Use of Less Trusted Source"}],"description":"SSL.com before 2025-04-19, when domain validation method 3.2.2.4.14 is used, processes certificate requests such that a trusted TLS certificate may be issued for the domain name of a requester's email address, even when the requester does not otherwise establish administrative control of that domain.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Business logic in SSL.com","id":"CVE-2025-43918","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"business_logic","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Path traversal in Mailman","id":"CVE-2025-43919"},"packages":[],"prev":{"headline":"Privilege escalation in Pritunl-Client","id":"CVE-2025-43917"},"products":["SSL.com"],"published":"2025-04-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-21","vendors":["SSL.com"]},"summary":"Attackers can obtain trusted TLS certificates for domains they do not control by exploiting a flaw in SSL.com's domain validation logic.","url":"https://insights.sbomify.com/CVE-2025-43918/"}