{"answers":{"affected":"2 open source packages ship an affected version, including org.grails:grails-core. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-12728 in the wild and no public exploit code.","fix":"Upgrade org.grails:grails-core to 3.3.10 or later.","what":"CVE-2019-12728 is a high-severity vulnerability in n/a, published on 4 Jun 2019. 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-12728 and fix it if it is affected.\n\nWhat it is: CVE-2019-12728 is a high-severity vulnerability in n/a, published on 4 Jun 2019. 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-12728 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- org.grails:grails-core (Maven): affected all versions; fixed in 3.3.10\n- org.grails:grails-core (Maven): affected all versions; fixed in 3.3.10\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-12728/ (Markdown: https://insights.sbomify.com/CVE-2019-12728/index.md)","id":"CVE-2019-12728","markdown":"https://insights.sbomify.com/CVE-2019-12728/index.md","name":"CVE-2019-12728","record":{"aliases":["GHSA-pmxf-4v8c-rwr7"],"analysis":{"component_type":"developer_tool","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Grails framework","requires_auth":"none","summary":"Grails framework used cleartext HTTP for SDKMan notifications, potentially allowing man-in-the-middle attacks to inject malicious code during dependency resolution.","user_interaction":"not_required","vuln_class":"supply_chain"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"grails","vendor":"grails"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.0/AC:H/AV:N/A:H/C:H/I:H/PR:N/S:U/UI:N","version":"3.0"},"cwes":[{"id":"CWE-494","name":"Download of Code Without Integrity Check"}],"description":"Grails before 3.3.10 used cleartext HTTP to resolve the SDKMan notification service. NOTE: users' apps were not resolving dependencies over cleartext HTTP.","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":"Incorrect Resource Transfer Between Spheres in Grails","id":"CVE-2019-12728","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":null,"products":[],"type":"supply_chain","year":"2019"},"n_packages":2,"n_references":2,"next":{"headline":"Other in n/a","id":"CVE-2019-12730"},"packages":[{"ecosystem":"Maven","fixed":["3.3.10"],"introduced":["0"],"last_affected":[],"package":"org.grails:grails-core","purl":null,"source":"GHSA-pmxf-4v8c-rwr7"},{"ecosystem":"Maven","fixed":["3.3.10"],"introduced":["0"],"last_affected":[],"package":"org.grails:grails-core","purl":"pkg:maven/org.grails/grails-core","source":"GHSA-pmxf-4v8c-rwr7"}],"prev":{"headline":"Denial of service in n/a","id":"CVE-2019-12727"},"products":["n/a"],"published":"2019-06-04","related":[{"cvss_score":9.8,"headline":"Grails framework Remote Code Execution via Data Binding","id":"CVE-2022-35912","kev_date_added":null,"published":"2022-07-19"},{"cvss_score":6.5,"headline":"Grails® data binding causes JVM crash and/or DoS","id":"CVE-2023-46131","kev_date_added":null,"published":"2023-12-20"}],"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-04","vendors":["n/a"]},"summary":"Grails framework used cleartext HTTP for SDKMan notifications, potentially allowing man-in-the-middle attacks to inject malicious code during dependency resolution.","url":"https://insights.sbomify.com/CVE-2019-12728/"}