{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-2499 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-2499 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-2499 is a medium-severity vulnerability in QNAP Systems Inc. QES, published on 24 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-2499 and fix it if it is affected.\n\nWhat it is: CVE-2020-2499 is a medium-severity vulnerability in QNAP Systems Inc. QES, published on 24 Dec 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-2499 in the wild and no public exploit code.\n\nAffected product: QNAP Systems Inc. QES. 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-2499/ (Markdown: https://insights.sbomify.com/CVE-2020-2499/index.md)","id":"CVE-2020-2499","markdown":"https://insights.sbomify.com/CVE-2020-2499/index.md","name":"CVE-2020-2499","record":{"aliases":["GHSA-fwrf-6v6g-jrvx"],"analysis":{"component_type":"operating_system","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"QNAP QES OS","requires_auth":"high_privilege","summary":"Attackers can log in using a hard-coded password in QES, leading to unauthorized access and potential account takeover.","user_interaction":"required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"qnap","cpe":[{"product":"qes","vendor":"qnap"}],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:L/AC:L/PR:H/UI:R/S:C/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-522","name":"Insufficiently Protected Credentials"},{"id":"CWE-259","name":"Use of Hard-coded Password"}],"description":"A hard-coded password vulnerability has been reported to affect earlier versions of QES. If exploited, this vulnerability could allow attackers to log in with a hard-coded password. QNAP has already fixed the issue in QES 2.1.1 Build 20200515 and later.","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":"Hard-coded Password Vulnerability in QES","id":"CVE-2020-2499","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2020"},"n_packages":0,"n_references":1,"next":{"headline":"Hardcoded credentials in Helpdesk","id":"CVE-2020-2500"},"packages":[],"prev":{"headline":"Cross-site scripting vulnerability in QTS and QuTS hero","id":"CVE-2020-2498"},"products":["QES"],"published":"2020-12-24","related":[{"cvss_score":9,"headline":"Stored cross-site scripting vulnerability in QES","id":"CVE-2020-2503","kev_date_added":null,"published":"2020-12-24"},{"cvss_score":5.8,"headline":"Absolute path traversal vulnerability in QES","id":"CVE-2020-2504","kev_date_added":null,"published":"2020-12-24"},{"cvss_score":2.3,"headline":"Sensitive information via generation of error messages vulnerability in QES","id":"CVE-2020-2505","kev_date_added":null,"published":"2020-12-24"}],"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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2024-09-17","vendors":["QNAP Systems Inc."]},"summary":"Attackers can log in using a hard-coded password in QES, leading to unauthorized access and potential account takeover.","url":"https://insights.sbomify.com/CVE-2020-2499/"}