{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-4412 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-4412 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-4412 is a medium-severity vulnerability in SparkLabs Viscosity, published on 27 May 2025. 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-4412 and fix it if it is affected.\n\nWhat it is: CVE-2025-4412 is a medium-severity vulnerability in SparkLabs Viscosity, published on 27 May 2025. 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-4412 in the wild and no public exploit code.\n\nAffected product: SparkLabs Viscosity. 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-4412/ (Markdown: https://insights.sbomify.com/CVE-2025-4412/index.md)","id":"CVE-2025-4412","markdown":"https://insights.sbomify.com/CVE-2025-4412/index.md","name":"CVE-2025-4412","record":{"aliases":["GHSA-496p-vfhp-58hp"],"analysis":{"component_type":"desktop_application","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"macOS VPN client","requires_auth":"low_privilege","summary":"Attackers can bypass macOS TCC restrictions by loading a malicious dylib into Viscosity, gaining unauthorized access to user-granted file resources.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"CERT-PL","cpe":[],"cvss":{"score":4.8,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"On macOS systems, by utilizing a Launch Agent and loading the viscosity_openvpn process from the application bundle, it is possible to load a dynamic library with Viscosity's TCC (Transparency, Consent, and Control) identity. The acquired resource access is limited without entitlements such as access to the camera or microphone. Only user-granted permissions for file resources apply. Access to other resources beyond granted-permissions requires user interaction with a system prompt asking for permission.\n\nThis issue was fixed in version 1.11.5 of Viscosity.","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":"TCC Bypass via Dylib Loading in Viscosity.app","id":"CVE-2025-4412","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Pixabay Images \u003c= 3.4 - Authenticated (Author+) Arbitrary File Upload","id":"CVE-2025-4413"},"packages":[],"prev":{"headline":"XSS in Dataprom Informatics' PACS-ACSS","id":"CVE-2025-4411"},"products":["Viscosity"],"published":"2025-05-27","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-06-06","vendors":["SparkLabs"]},"summary":"Attackers can bypass macOS TCC restrictions by loading a malicious dylib into Viscosity, gaining unauthorized access to user-granted file resources.","url":"https://insights.sbomify.com/CVE-2025-4412/"}