{"answers":{"affected":"2 open source packages ship an affected version, including org.eclipse.milo:sdk-client. It affects 2 products.","exploited":"There is no known exploitation of CVE-2019-19135 in the wild and no public exploit code.","fix":"Upgrade org.eclipse.milo:sdk-client to 0.3.6 or later.","what":"CVE-2019-19135 is a high-severity vulnerability in n/a, published on 16 Mar 2020. 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-19135 and fix it if it is affected.\n\nWhat it is: CVE-2019-19135 is a high-severity vulnerability in n/a, published on 16 Mar 2020. 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-19135 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.eclipse.milo:sdk-client (Maven): affected all versions; fixed in 0.3.6\n- org.eclipse.milo:sdk-client (Maven): affected all versions; fixed in 0.3.6\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-19135/ (Markdown: https://insights.sbomify.com/CVE-2019-19135/index.md)","id":"CVE-2019-19135","markdown":"https://insights.sbomify.com/CVE-2019-19135/index.md","name":"CVE-2019-19135","record":{"aliases":["GHSA-pq4w-qm9g-qx68"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"OPC UA .NET Standard","requires_auth":"none","summary":"Insufficient randomness in OPC UA .NET Standard allows man-in-the-middle attackers to reuse encrypted user credentials, risking account takeover.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"netstandard.opc.ua","vendor":"opcfoundation"},{"product":"ua-.netstandard","vendor":"opcfoundation"}],"cvss":{"score":7.4,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-330","name":"Use of Insufficiently Random Values"}],"description":"In OPC Foundation OPC UA .NET Standard codebase 1.4.357.28, servers do not create sufficiently random numbers in OPCFoundation.NetStandard.Opc.Ua before 1.4.359.31, which allows man in the middle attackers to reuse encrypted user credentials sent over the network.","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Insufficient Nonce Validation in Eclipse Milo Client","id":"CVE-2019-19135","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"weak_cryptography","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2019-19138"},"packages":[{"ecosystem":"Maven","fixed":["0.3.6"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.milo:sdk-client","purl":null,"source":"GHSA-pq4w-qm9g-qx68"},{"ecosystem":"Maven","fixed":["0.3.6"],"introduced":["0"],"last_affected":[],"package":"org.eclipse.milo:sdk-client","purl":"pkg:maven/org.eclipse.milo/sdk-client","source":"GHSA-pq4w-qm9g-qx68"}],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-19134"},"products":["n/a"],"published":"2020-03-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"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":"Insufficient randomness in OPC UA .NET Standard allows man-in-the-middle attackers to reuse encrypted user credentials, risking account takeover.","url":"https://insights.sbomify.com/CVE-2019-19135/"}