{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-25057 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-25057 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-25057 is a high-severity unsafe deserialization vulnerability in n/a, published on 14 Feb 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-25057 and fix it if it is affected.\n\nWhat it is: CVE-2019-25057 is a high-severity unsafe deserialization vulnerability in n/a, published on 14 Feb 2022. 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-2019-25057 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-2019-25057/ (Markdown: https://insights.sbomify.com/CVE-2019-25057/index.md)","id":"CVE-2019-25057","markdown":"https://insights.sbomify.com/CVE-2019-25057/index.md","name":"CVE-2019-25057","record":{"aliases":["GHSA-wwp3-5348-34gx"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Corda distributed ledger","requires_auth":"none","summary":"An attacker can modify serialized data meaning via a custom serializer, potentially leading to code execution in Corda applications.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"corda","vendor":"r3"}],"cvss":{"score":7.5,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N","version":"3.1"},"cwes":[],"description":"In Corda before 4.1, the meaning of serialized data can be modified via an attacker-controlled CustomSerializer.","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":"Deserialization in n/a","id":"CVE-2019-25057","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2019"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2019-25058"},"packages":[],"prev":{"headline":"Information disclosure in n/a","id":"CVE-2019-25056"},"products":["n/a"],"published":"2022-02-14","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"An attacker can modify serialized data meaning via a custom serializer, potentially leading to code execution in Corda applications.","url":"https://insights.sbomify.com/CVE-2019-25057/"}