{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32407 exists.","fix":"No fix has been published for CVE-2025-32407 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32407 is a medium-severity vulnerability in n/a, published on 16 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-32407 and fix it if it is affected.\n\nWhat it is: CVE-2025-32407 is a medium-severity vulnerability in n/a, published on 16 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-32407 exists.\n\nAffected product: n/a. 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-32407/ (Markdown: https://insights.sbomify.com/CVE-2025-32407/index.md)","id":"CVE-2025-32407","markdown":"https://insights.sbomify.com/CVE-2025-32407/index.md","name":"CVE-2025-32407","record":{"aliases":["GHSA-2hgg-g6cr-365f"],"analysis":{"component_type":"browser","fix_type":"end_of_life","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Samsung Internet browser","requires_auth":"none","summary":"Samsung Internet for Galaxy Watch fails to validate TLS certificates, enabling Man-in-the-Middle attacks to intercept or modify user traffic.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"internet","vendor":"samsung"}],"cvss":{"score":5.9,"severity":"medium","source":"cisa-adp","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":"Samsung Internet for Galaxy Watch version 5.0.9, available up until Samsung Galaxy Watch 3, does not properly validate TLS certificates, allowing for an attacker to impersonate any and all websites visited by the user. This is a critical misconfiguration in the way the browser validates the identity of the server. It negates the use of HTTPS as a secure channel, allowing for Man-in-the-Middle attacks, stealing sensitive information or modifying incoming and outgoing traffic. NOTE: This vulnerability is in an end-of-life product that is no longer maintained by the vendor.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-05-14","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-05-14T18:50:28Z","kind":"github_poc","ref":"https://github.com/diegovargasj/CVE-2025-32407","stars":0,"title":"CVE-2025-32407 PoC"}],"tier":"weaponised"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2025-32407","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in IAM","id":"CVE-2025-32408"},"packages":[],"prev":{"headline":"XML external entity in Backup \u0026 Replication Director","id":"CVE-2025-32406"},"products":["n/a"],"published":"2025-05-16","related":[{"cvss_score":7.8,"headline":"Other in Samsug Internet","id":"CVE-2021-25400","kev_date_added":null,"published":"2021-06-11"},{"cvss_score":7.8,"headline":"Missing authorization in Samsung Internet","id":"CVE-2021-25418","kev_date_added":null,"published":"2021-06-11"},{"cvss_score":6.8,"headline":"Code injection in Samsung Internet","id":"CVE-2024-20838","kev_date_added":null,"published":"2024-03-05"},{"cvss_score":6.5,"headline":"Security feature bypass in Samsung Internet","id":"CVE-2023-30674","kev_date_added":null,"published":"2023-07-06"},{"cvss_score":6.5,"headline":"Other in Samsung Internet","id":"CVE-2022-22290","kev_date_added":null,"published":"2022-01-14"},{"cvss_score":6.5,"headline":"Security feature bypass in Samsung Internet","id":"CVE-2021-25466","kev_date_added":null,"published":"2021-09-09"},{"cvss_score":6.5,"headline":"Other in Samsung Internet","id":"CVE-2021-25419","kev_date_added":null,"published":"2021-06-11"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-17","vendors":["n/a"]},"summary":"Samsung Internet for Galaxy Watch fails to validate TLS certificates, enabling Man-in-the-Middle attacks to intercept or modify user traffic.","url":"https://insights.sbomify.com/CVE-2025-32407/"}