{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-30042 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-30042 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-30042 is a critical authentication bypass vulnerability in CGM CLININET, published on 2 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-30042 and fix it if it is affected.\n\nWhat it is: CVE-2025-30042 is a critical authentication bypass vulnerability in CGM CLININET, published on 2 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-30042 in the wild and no public exploit code.\n\nAffected product: CGM CLININET. 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-30042/ (Markdown: https://insights.sbomify.com/CVE-2025-30042/index.md)","id":"CVE-2025-30042","markdown":"https://insights.sbomify.com/CVE-2025-30042/index.md","name":"CVE-2025-30042","record":{"aliases":["GHSA-rfwf-h4fr-xr3g"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["account_takeover","security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Medical clinic software","requires_auth":"none","summary":"Attackers can bypass smart card authentication in CGM CLININET by using only the certificate number, gaining unauthorized access without the physical card or private key.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[{"product":"clininet","vendor":"cgm"}],"cvss":{"score":9,"severity":"critical","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H","version":"4.0"},"cwes":[{"id":"CWE-603","name":"Use of Client-Side Authentication"}],"description":"The CGM CLININET system provides smart card authentication; however, authentication is conducted locally on the client device, and, in reality, only the certificate number is used for access verification. As a result, possession of the certificate number alone is sufficient for authentication, regardless of the actual presence of the smart card or ownership of the private key.","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":"Session generation possible with certificate number only","id":"CVE-2025-30042","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Missing Authentication in CGM CLININET","id":"CVE-2025-30043"},"packages":[],"prev":{"headline":"Missing authentication in APIs returning statistical data along with session IDs","id":"CVE-2025-30041"},"products":["CGM CLININET"],"published":"2026-03-02","related":[{"cvss_score":7.1,"headline":"Insecure Direct Object Reference Message ID","id":"CVE-2025-58402","kev_date_added":null,"published":"2026-03-02"},{"cvss_score":5.3,"headline":"Lack of protection mechanisms against Clickjacking attacks","id":"CVE-2025-58405","kev_date_added":null,"published":"2026-03-02"},{"cvss_score":5.3,"headline":"Lack of HTTP Response Headers","id":"CVE-2025-58406","kev_date_added":null,"published":"2026-03-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":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-02","vendors":["CGM"]},"summary":"Attackers can bypass smart card authentication in CGM CLININET by using only the certificate number, gaining unauthorized access without the physical card or private key.","url":"https://insights.sbomify.com/CVE-2025-30042/"}