{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26526 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26526 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26526 is a medium-severity vulnerability in n/a, published on 2 Oct 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-2020-26526 and fix it if it is affected.\n\nWhat it is: CVE-2020-26526 is a medium-severity vulnerability in n/a, published on 2 Oct 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-2020-26526 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-2020-26526/ (Markdown: https://insights.sbomify.com/CVE-2020-26526/index.md)","id":"CVE-2020-26526","markdown":"https://insights.sbomify.com/CVE-2020-26526/index.md","name":"CVE-2020-26526","record":{"aliases":["GHSA-38c2-vx55-m3wp"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Damstra Smart Asset","requires_auth":"none","summary":"Attackers can enumerate valid usernames on the login page due to inconsistent error messages, facilitating targeted attacks.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"smart_asset","vendor":"damstratechnology"}],"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 Damstra Smart Asset 2020.7. It is possible to enumerate valid usernames on the login page. The application sends a different server response when the username is invalid than when the username is valid (\"Unable to find an APIDomain\" versus \"Wrong email or password\").","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2020-10-02","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2020-10-02T07:15:52Z","kind":"github_poc","ref":"https://github.com/lukaszstu/SmartAsset-UE-CVE-2020-26526","stars":0,"title":"It is possible to enumerate valid usernames on the login page."}],"tier":"poc_unverified"},"has_fix":null,"headline":"Information disclosure in n/a","id":"CVE-2020-26526","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2020"},"n_packages":0,"n_references":3,"next":{"headline":"Misconfiguration in n/a","id":"CVE-2020-26527"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2020-26525"},"products":["n/a"],"published":"2020-10-02","related":[{"cvss_score":9.8,"headline":"Misconfiguration in n/a","id":"CVE-2020-26527","kev_date_added":null,"published":"2020-10-02"},{"cvss_score":9.1,"headline":"SQL injection in n/a","id":"CVE-2020-26525","kev_date_added":null,"published":"2020-10-02"}],"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":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-08-04","vendors":["n/a"]},"summary":"Attackers can enumerate valid usernames on the login page due to inconsistent error messages, facilitating targeted attacks.","url":"https://insights.sbomify.com/CVE-2020-26526/"}