{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28329 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-28329 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-28329 is a critical vulnerability in n/a, published on 24 Nov 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-28329 and fix it if it is affected.\n\nWhat it is: CVE-2020-28329 is a critical vulnerability in n/a, published on 24 Nov 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-28329 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-28329/ (Markdown: https://insights.sbomify.com/CVE-2020-28329/index.md)","id":"CVE-2020-28329","markdown":"https://insights.sbomify.com/CVE-2020-28329/index.md","name":"CVE-2020-28329","record":{"aliases":["GHSA-r54x-g9vf-56fv"],"analysis":{"component_type":"iot_embedded","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Barco wePresent firmware","requires_auth":"none","summary":"Attackers can extract hardcoded API credentials from the firmware to access administrative functions, requiring a firmware upgrade.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"wepresent_wipg-1600w_firmware","vendor":"barco"}],"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":[{"id":"CWE-798","name":"Use of Hard-coded Credentials"}],"description":"Barco wePresent WiPG-1600W firmware includes a hardcoded API account and password that is discoverable by inspecting the firmware image. A malicious actor could use this password to access authenticated, administrative functions in the API. Affected Version(s): 2.5.1.8, 2.5.0.25, 2.5.0.24, 2.4.1.19.","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":"Hardcoded credentials in n/a","id":"CVE-2020-28329","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":"Information disclosure in n/a","id":"CVE-2020-28330"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2020-28328"},"products":["n/a"],"published":"2020-11-24","related":[{"cvss_score":9.8,"headline":"Other in n/a","id":"CVE-2020-28332","kev_date_added":null,"published":"2020-11-24"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2020-28333","kev_date_added":null,"published":"2020-11-24"},{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-28334","kev_date_added":null,"published":"2020-11-24"},{"cvss_score":7.5,"headline":"Missing authorization in n/a","id":"CVE-2020-28331","kev_date_added":null,"published":"2020-11-24"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2020-28330","kev_date_added":null,"published":"2020-11-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-08-04","vendors":["n/a"]},"summary":"Attackers can extract hardcoded API credentials from the firmware to access administrative functions, requiring a firmware upgrade.","url":"https://insights.sbomify.com/CVE-2020-28329/"}