{"answers":{"affected":"","exploited":"There is no known exploitation of SUSE-SU-2025:20336-1 in the wild and no public exploit code.","fix":"Apply the vendor's patch.","what":"SUSE-SU-2025:20336-1 is a vulnerability in ca-certificates-mozilla, published on 21 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 SUSE-SU-2025:20336-1 and fix it if it is affected.\n\nWhat it is: SUSE-SU-2025:20336-1 is a vulnerability in ca-certificates-mozilla, published on 21 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 SUSE-SU-2025:20336-1 in the wild and no public exploit code.\n\nAffected product: ca-certificates-mozilla. 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/SUSE-SU-2025-20336-1/ (Markdown: https://insights.sbomify.com/SUSE-SU-2025-20336-1/index.md)","id":"SUSE-SU-2025:20336-1","markdown":"https://insights.sbomify.com/SUSE-SU-2025-20336-1/index.md","name":"SUSE-SU-2025:20336-1","record":{"aliases":[],"analysis":{"component_type":"operating_system","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"SUSE CA certificates","requires_auth":"none","summary":"An attacker could bypass certificate trust restrictions because distrusted certificates were not correctly removed from the trust store.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This update for ca-certificates-mozilla fixes the following issues:\n\n- test for a concretely missing certificate rather than\n  just the directory, as the latter is now also provided by\n  openssl-3\n\n- Re-create java-cacerts with SOURCE_DATE_EPOCH set\n  for reproducible builds (bsc#1229003)\n\n- explicit remove distrusted certs, as the distrust does not get exported\n  correctly and the SSL certs are still trusted. (bsc#1240343)\n  - Entrust.net Premium 2048 Secure Server CA\n  - Entrust Root Certification Authority\n  - AffirmTrust Commercial\n  - AffirmTrust Networking\n  - AffirmTrust Premium\n  - AffirmTrust Premium ECC\n  - Entrust Root Certification Authority - G2\n  - Entrust Root Certification Authority - EC1\n  - GlobalSign Root E46\n  - GLOBALTRUST 2020\n\n- pass file argument to awk (bsc#1240009)\n\n- update to 2.74 state of Mozilla SSL root CAs:\n  Removed:\n  * SwissSign Silver CA - G2\n  Added:\n  * D-TRUST BR Root CA 2 2023\n  * D-TRUST EV Root CA 2 2023\n\n- remove extensive signature printing in comments of the cert\n  bundle\n\n- Define two macros to break a build cycle with p11-kit.\n\n- Updated to 2.72 state of Mozilla SSL root CAs (bsc#1234798)\n  Removed:\n  - SecureSign RootCA11\n  - Security Communication RootCA3\n  Added:\n  - TWCA CYBER Root CA\n  - TWCA Global Root CA G2\n  - SecureSign Root CA12\n  - SecureSign Root CA14\n  - SecureSign Root CA15","ecosystems":["SUSE:Linux Micro 6.0"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":true,"headline":"Security update for ca-certificates-mozilla","id":"SUSE-SU-2025:20336-1","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"SUSE:Linux Micro 6.0","fixed":["2.74-1.1"],"introduced":["0"],"last_affected":[],"package":"ca-certificates-mozilla","purl":"pkg:rpm/suse/ca-certificates-mozilla\u0026distro=SUSE%20Linux%20Micro%206.0","source":"SUSE-SU-2025:20336-1"}],"products":null,"published":"2025-05-21","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"SUSE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An attacker could bypass certificate trust restrictions because distrusted certificates were not correctly removed from the trust store.","url":"https://insights.sbomify.com/SUSE-SU-2025-20336-1/"}