{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-16374 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-16374 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-16374 is a critical authentication bypass vulnerability in n/a, published on 13 Aug 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-16374 and fix it if it is affected.\n\nWhat it is: CVE-2019-16374 is a critical authentication bypass vulnerability in n/a, published on 13 Aug 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-16374 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-16374/ (Markdown: https://insights.sbomify.com/CVE-2019-16374/index.md)","id":"CVE-2019-16374","markdown":"https://insights.sbomify.com/CVE-2019-16374/index.md","name":"CVE-2019-16374","record":{"aliases":["GHSA-pmcq-jc5w-xg5x"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Pega Platform","requires_auth":"none","summary":"Attackers can bypass access control in Pega Platform by using wildcards in usernames, allowing unauthorized access to the system.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"platform","vendor":"pega"}],"cvss":{"score":9.8,"severity":"critical","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"Pega Platform 8.2.1 allows LDAP injection because a username can contain a * character and can be of unlimited length. An attacker can specify four characters of a username, followed by the * character, to bypass access control.","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":"Auth bypass in n/a","id":"CVE-2019-16374","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2019"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-16375"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2019-16371"},"products":["n/a"],"published":"2020-08-13","related":[{"cvss_score":8.9,"headline":"Cross-site scripting in n/a","id":"CVE-2020-8773","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":8.9,"headline":"Cross-site scripting in n/a","id":"CVE-2020-8775","kev_date_added":null,"published":"2020-04-29"},{"cvss_score":8.5,"headline":"Server-side request forgery in Pega Platform","id":"CVE-2023-50165","kev_date_added":null,"published":"2024-01-31"},{"cvss_score":6.1,"headline":"Cross-site scripting in Pega Platform","id":"CVE-2023-50166","kev_date_added":null,"published":"2024-01-31"},{"cvss_score":4.6,"headline":"Cross-site scripting in Pega Platform","id":"CVE-2023-32087","kev_date_added":null,"published":"2023-10-18"},{"cvss_score":4.6,"headline":"Cross-site scripting in Pega Platform","id":"CVE-2023-32088","kev_date_added":null,"published":"2023-10-18"}],"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":"Attackers can bypass access control in Pega Platform by using wildcards in usernames, allowing unauthorized access to the system.","url":"https://insights.sbomify.com/CVE-2019-16374/"}