{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-21604 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-21604 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-21604 is a medium-severity vulnerability in moyangzhan langchain4j-aideepin, published on 6 Jan 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-21604 and fix it if it is affected.\n\nWhat it is: CVE-2025-21604 is a medium-severity vulnerability in moyangzhan langchain4j-aideepin, published on 6 Jan 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 CVE-2025-21604 in the wild and no public exploit code.\n\nAffected product: moyangzhan langchain4j-aideepin. 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-21604/ (Markdown: https://insights.sbomify.com/CVE-2025-21604/index.md)","id":"CVE-2025-21604","markdown":"https://insights.sbomify.com/CVE-2025-21604/index.md","name":"CVE-2025-21604","record":{"aliases":["GHSA-cv5r-73vf-8x7v"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Java RAG library","requires_auth":"none","summary":"Attackers can cause file upload conflicts in LangChain4j-AIDeepin by exploiting weak MD5 hashing, potentially overwriting or corrupting stored files.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-328","name":"Use of Weak Hash"}],"description":"LangChain4j-AIDeepin is a Retrieval enhancement generation (RAG) project. Prior to 3.5.0, LangChain4j-AIDeepin uses MD5 to hash files, which may cause file upload conflicts. This issue is fixed in 3.5.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"LangChain4j-AIDeepin Using MD5 to Hash files may cause file upload conflicts","id":"CVE-2025-21604","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Redis DoS Vulnerability due to unlimited growth of output buffers abused by unauthenticated client","id":"CVE-2025-21605"},"packages":[],"prev":{"headline":"Cross-site scripting in MZK-DP300N","id":"CVE-2025-21603"},"products":["langchain4j-aideepin"],"published":"2025-01-06","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-01-06","vendors":["moyangzhan"]},"summary":"Attackers can cause file upload conflicts in LangChain4j-AIDeepin by exploiting weak MD5 hashing, potentially overwriting or corrupting stored files.","url":"https://insights.sbomify.com/CVE-2025-21604/"}