{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2019-19774 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2019-19774 yet. Limit exposure of the affected software until one is available.","what":"CVE-2019-19774 is a high-severity vulnerability in n/a, published on 13 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2019-19774 and fix it if it is affected.\n\nWhat it is: CVE-2019-19774 is a high-severity vulnerability in n/a, published on 13 Dec 2019. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2019-19774 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-19774/ (Markdown: https://insights.sbomify.com/CVE-2019-19774/index.md)","id":"CVE-2019-19774","markdown":"https://insights.sbomify.com/CVE-2019-19774/index.md","name":"CVE-2019-19774","record":{"aliases":["GHSA-5855-w2f6-pwrj"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"EventLog Analyzer","requires_auth":"low_privilege","summary":"Attackers can bypass query restrictions to retrieve MD5 hashes of administrative credentials from the database via a specific SQL query.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"manageengine_eventlog_analyzer","vendor":"zohocorp"}],"cvss":{"score":8.8,"severity":"high","source":"nvd","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[],"description":"An issue was discovered in Zoho ManageEngine EventLog Analyzer 10.0 SP1 before Build 12110. By running \"select hostdetails from hostdetails\" at the /event/runquery.do endpoint, it is possible to bypass the security restrictions that prevent even administrative users from viewing credential data stored in the database, and recover the MD5 hashes of the accounts used to authenticate the ManageEngine platform to the managed machines on the network (most often administrative accounts). Specifically, this bypasses these restrictions: a query cannot mention password, and a query result cannot have a password column.","ecosystems":[],"exploits":{"exploitdb":1,"first_seen":"2020-02-24","github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-02-24","kind":"exploitdb","ref":"48119","stars":null,"title":"ManageEngine EventLog Analyzer 10.0 - Information Disclosure"}],"tier":"poc_unverified"},"has_fix":null,"headline":"Security feature bypass in n/a","id":"CVE-2019-19774","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2019"},"n_packages":0,"n_references":3,"next":{"headline":"Open redirect in n/a","id":"CVE-2019-19775"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2019-19773"},"products":["n/a"],"published":"2019-12-13","related":[{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2021-28959","kev_date_added":null,"published":"2021-04-30"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2014-6038","kev_date_added":null,"published":"2020-01-13"},{"cvss_score":7.5,"headline":"Information disclosure in n/a","id":"CVE-2014-6039","kev_date_added":null,"published":"2020-01-13"},{"cvss_score":7.5,"headline":"SQL injection in n/a","id":"CVE-2015-7387","kev_date_added":null,"published":"2015-09-28"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2014-6037","kev_date_added":null,"published":"2014-10-26"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2014-6043","kev_date_added":null,"published":"2014-09-11"}],"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)"},{"class":"attribution","licence":"GPL-2.0-or-later","name":"Exploit-DB"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-05","vendors":["n/a"]},"summary":"Attackers can bypass query restrictions to retrieve MD5 hashes of administrative credentials from the database via a specific SQL query.","url":"https://insights.sbomify.com/CVE-2019-19774/"}