{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-32874 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-32874 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-32874 is a high-severity vulnerability in n/a, published on 16 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-32874 and fix it if it is affected.\n\nWhat it is: CVE-2025-32874 is a high-severity vulnerability in n/a, published on 16 Jul 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-32874 in the wild and no public exploit code.\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-32874/ (Markdown: https://insights.sbomify.com/CVE-2025-32874/index.md)","id":"CVE-2025-32874","markdown":"https://insights.sbomify.com/CVE-2025-32874/index.md","name":"CVE-2025-32874","record":{"aliases":["GHSA-fm6w-39g9-r4vh"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Kaseya Network Detective","requires_auth":"low_privilege","summary":"Attackers can decrypt stored passwords due to deterministic encryption with hardcoded keys and static salts in Kaseya Network Detective.","user_interaction":"required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-326","name":"Inadequate Encryption Strength"}],"description":"An issue was discovered in Kaseya Rapid Fire Tools Network Detective through 2.0.16.0. A vulnerability exists in the EncryptionUtil class because symmetric encryption is implemented in a deterministic and non-randomized fashion. The method Encrypt(byte[] clearData) derives both the encryption key and the IV from a fixed, hardcoded input by using a static salt value. As a result, identical plaintext inputs always produce identical ciphertext outputs. This is true for both FIPS and non-FIPS generated passwords. In other words, there is a cryptographic implementation flaw in the password encryption mechanism. Although there are multiple encryption methods grouped under FIPS and non-FIPS classifications, the logic consistently results in predictable and reversible encrypted outputs due to the lack of per-operation randomness and encryption authentication.","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":"Weak cryptography in n/a","id":"CVE-2025-32874","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Weak cryptography in n/a","id":"CVE-2025-32875"},"packages":[],"prev":{"headline":"Django has a denial-of-service possibility in strip_tags()","id":"CVE-2025-32873"},"products":["n/a"],"published":"2025-07-16","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":"total"},"state":"PUBLISHED","updated":"2025-11-24","vendors":["n/a"]},"summary":"Attackers can decrypt stored passwords due to deterministic encryption with hardcoded keys and static salts in Kaseya Network Detective.","url":"https://insights.sbomify.com/CVE-2025-32874/"}