{"answers":{"affected":"2 open source packages ship an affected version, including devise. It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16109 in the wild and no public exploit code.","fix":"Upgrade devise to 4.7.1 or later.","what":"CVE-2019-16109 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Sep 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-16109 and fix it if it is affected.\n\nWhat it is: CVE-2019-16109 is a medium-severity authentication bypass vulnerability in n/a, published on 8 Sep 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-16109 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- devise (RubyGems): affected all versions; fixed in 4.7.1\n- devise (RubyGems): affected all versions; fixed in 4.7.1\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-16109/ (Markdown: https://insights.sbomify.com/CVE-2019-16109/index.md)","id":"CVE-2019-16109","markdown":"https://insights.sbomify.com/CVE-2019-16109/index.md","name":"CVE-2019-16109","record":{"aliases":["GHSA-fcjw-8rhj-gwwc","UBUNTU-CVE-2019-16109"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":true,"product_category":"Ruby authentication library","requires_auth":"none","summary":"Attackers can bypass account confirmation if database records have blank tokens, potentially taking over accounts in Devise Ruby library.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"devise","vendor":"plataformatec"}],"cvss":{"score":5.3,"severity":"medium","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[],"description":"An issue was discovered in Plataformatec Devise before 4.7.1. It confirms accounts upon receiving a request with a blank confirmation_token, if a database record has a blank value in the confirmation_token column. (However, there is no scenario within Devise itself in which such database records would exist.)","ecosystems":["RubyGems"],"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":"Authentication Bypass in Devise","id":"CVE-2019-16109","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"RubyGems","product":null,"products":[],"type":"auth_bypass","year":"2019"},"n_packages":2,"n_references":3,"next":{"headline":"Code injection in n/a","id":"CVE-2019-16110"},"packages":[{"ecosystem":"RubyGems","fixed":["4.7.1"],"introduced":["0"],"last_affected":[],"package":"devise","purl":null,"source":"GHSA-fcjw-8rhj-gwwc"},{"ecosystem":"RubyGems","fixed":["4.7.1"],"introduced":["0"],"last_affected":[],"package":"devise","purl":"pkg:gem/devise","source":"GHSA-fcjw-8rhj-gwwc"}],"prev":{"headline":"phpBB arbitrary CSS injection","id":"CVE-2019-16108"},"products":["n/a"],"published":"2019-09-08","related":[{"cvss_score":9.8,"headline":"devise Time-of-check Time-of-use Race Condition vulnerability","id":"CVE-2019-5421","kev_date_added":null,"published":"2019-04-03"}],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass account confirmation if database records have blank tokens, potentially taking over accounts in Devise Ruby library.","url":"https://insights.sbomify.com/CVE-2019-16109/"}