{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-46434 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-46434 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-46434 is a medium-severity vulnerability in n/a, published on 28 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-46434 and fix it if it is affected.\n\nWhat it is: CVE-2021-46434 is a medium-severity vulnerability in n/a, published on 28 Mar 2022. 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-2021-46434 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-2021-46434/ (Markdown: https://insights.sbomify.com/CVE-2021-46434/index.md)","id":"CVE-2021-46434","markdown":"https://insights.sbomify.com/CVE-2021-46434/index.md","name":"CVE-2021-46434","record":{"aliases":["GHSA-gg4q-gffx-2ffc"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"EMQ X Dashboard","requires_auth":"none","summary":"An attacker can enumerate valid usernames via the login API due to inconsistent error responses, facilitating targeted attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"emqx","vendor":"emqx"}],"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":"EMQ X Dashboard V3.0.0 is affected by username enumeration in the \"/api /v3/auth\" interface. When a user login, the application returns different results depending on whether the account is correct, that allowed an attacker to determine if a given username was valid","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Information disclosure in n/a","id":"CVE-2021-46434","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"SQL injection in n/a","id":"CVE-2021-46436"},"packages":[],"prev":{"headline":"Sandbox bypass in fenom","id":"CVE-2021-46433"},"products":["n/a"],"published":"2022-03-28","related":[{"cvss_score":6.5,"headline":"Path traversal in n/a","id":"CVE-2023-37781","kev_date_added":null,"published":"2023-07-17"},{"cvss_score":2.3,"headline":"EMQX QoS 2 PUBLISH Packet emqx_persistent_session_ds.erl race condition","id":"CVE-2026-8741","kev_date_added":null,"published":"2026-05-17"}],"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-04","vendors":["n/a"]},"summary":"An attacker can enumerate valid usernames via the login API due to inconsistent error responses, facilitating targeted attacks.","url":"https://insights.sbomify.com/CVE-2021-46434/"}