{"answers":{"affected":"3 open source packages ship an affected version, including github.com/rancher/rancher. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-11881 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-11881 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-11881 is a medium-severity vulnerability in n/a, published on 10 Jun 2019."},"fix_prompt":"Check this codebase for CVE-2019-11881 and fix it if it is affected.\n\nWhat it is: CVE-2019-11881 is a medium-severity vulnerability in n/a, published on 10 Jun 2019. \nExploitation: There is no known exploitation of CVE-2019-11881 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/rancher/rancher (Go): affected all versions; no fix listed\n- github.com/rancher/rancher (Go): affected all versions up to 2.1.4; no fix listed\n- github.com/rancher/rancher (Go): affected all versions up to 2.1.4; no fix listed\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-11881/ (Markdown: https://insights.sbomify.com/CVE-2019-11881/index.md)","id":"CVE-2019-11881","markdown":"https://insights.sbomify.com/CVE-2019-11881/index.md","name":"CVE-2019-11881","record":{"aliases":["GHSA-2p4g-jrmx-r34m","GO-2024-2761"],"analysis":null,"analysis_generated_by":null,"assigner":"mitre","cpe":[{"product":"rancher","vendor":"suse"}],"cvss":{"score":4.7,"severity":"medium","source":"nvd","vector":"CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:N/I:L/A:N","version":"3.0"},"cwes":[],"description":"A vulnerability exists in Rancher before 2.2.4 in the login component, where the errorMsg parameter can be tampered to display arbitrary content, filtering tags but not special characters or symbols. There's no other limitation of the message, allowing malicious users to lure legitimate users to visit phishing sites with scare tactics, e.g., displaying a \"This version of Rancher is outdated, please visit https://malicious.rancher.site/upgrading\" message.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":"2019-05-24","github_poc":1,"max_poc_stars":3,"metasploit":0,"nuclei":0,"refs":[{"date":"2019-05-24T00:09:21Z","kind":"github_poc","ref":"https://github.com/MauroEldritch/VanCleef","stars":3,"title":"Exploit for CVE-2019-11881 (Rancher 2.1.4 Web Parameter Tampering)"}],"tier":"poc_unverified"},"has_fix":false,"headline":"Rancher Login Parameter Can Be Edited","id":"CVE-2019-11881","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":null,"year":"2019"},"n_packages":3,"n_references":4,"next":{"headline":"Information disclosure in n/a","id":"CVE-2019-11884"},"packages":[{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":[],"package":"github.com/rancher/rancher","purl":"pkg:golang/github.com/rancher/rancher","source":"GO-2024-2761"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["2.1.4"],"package":"github.com/rancher/rancher","purl":null,"source":"GHSA-2p4g-jrmx-r34m"},{"ecosystem":"Go","fixed":[],"introduced":["0"],"last_affected":["2.1.4"],"package":"github.com/rancher/rancher","purl":"pkg:golang/github.com/rancher/rancher","source":"GHSA-2p4g-jrmx-r34m"}],"prev":{"headline":"SQL injection in n/a","id":"CVE-2019-11880"},"products":["n/a"],"published":"2019-06-10","related":[{"cvss_score":9.9,"headline":"Rancher vulnerable to Privilege Escalation via manipulation of Secrets","id":"CVE-2023-22647","kev_date_added":null,"published":"2023-06-01"},{"cvss_score":9.9,"headline":"Rancher Webhook is misconfigured during upgrade process","id":"CVE-2023-22651","kev_date_added":null,"published":"2023-05-04"},{"cvss_score":9.9,"headline":"Rancher: Exposure of sensitive fields","id":"CVE-2022-43757","kev_date_added":null,"published":"2023-02-07"},{"cvss_score":9.9,"headline":"Rancher: Plaintext storage and exposure of credentials in Rancher API and cluster.management.cattle.io object","id":"CVE-2021-36782","kev_date_added":null,"published":"2022-09-07"},{"cvss_score":9.9,"headline":"Rancher: Failure to properly sanitize credentials in cluster template answers","id":"CVE-2021-36783","kev_date_added":null,"published":"2022-09-07"},{"cvss_score":9.8,"headline":"Rancher Recreates Default User With Known Password Despite Deletion","id":"CVE-2019-11202","kev_date_added":null,"published":"2019-07-30"},{"cvss_score":9.5,"headline":"SAML Authentication Replay in Rancher","id":"CVE-2026-44946","kev_date_added":null,"published":"2026-06-30"}],"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":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-12-04","vendors":["n/a"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2019-11881/"}