{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-0418 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-0418 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-0418 is a medium-severity vulnerability in Valmet DNA, published on 1 Apr 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-0418 and fix it if it is affected.\n\nWhat it is: CVE-2025-0418 is a medium-severity vulnerability in Valmet DNA, published on 1 Apr 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-0418 in the wild and no public exploit code.\n\nAffected product: Valmet DNA. 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-0418/ (Markdown: https://insights.sbomify.com/CVE-2025-0418/index.md)","id":"CVE-2025-0418","markdown":"https://insights.sbomify.com/CVE-2025-0418/index.md","name":"CVE-2025-0418","record":{"aliases":["GHSA-mcmj-q426-5fcx"],"analysis":{"component_type":"ics_ot","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Valmet DNA","requires_auth":"none","summary":"Attackers with local access can read user passwords stored in plain text, compromising account security.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC-FI","cpe":[],"cvss":{"score":5.2,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:P/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:H/SC:N/SI:N/SA:N/R:A/V:D/RE:L/U:Green","version":"4.0"},"cwes":[{"id":"CWE-312","name":"Cleartext Storage of Sensitive Information"}],"description":"Valmet DNA user passwords in plain text. This practice poses a security risk as attackers who gain access to local project data can read the passwords.","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":"Valmet DNA user passwords in plain text","id":"CVE-2025-0418","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"XSS in Mikrogrup's Zirve Nova","id":"CVE-2025-0419"},"packages":[],"prev":{"headline":"Valmet DNA Lack of protection against brute force attacks","id":"CVE-2025-0417"},"products":["Valmet DNA"],"published":"2025-04-01","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-04-01","vendors":["Valmet"]},"summary":"Attackers with local access can read user passwords stored in plain text, compromising account security.","url":"https://insights.sbomify.com/CVE-2025-0418/"}