{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-28333 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-28333 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-28333 is a critical authentication bypass 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-28333 and fix it if it is affected.\n\nWhat it is: CVE-2020-28333 is a critical authentication bypass 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-28333 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-28333/ (Markdown: https://insights.sbomify.com/CVE-2020-28333/index.md)","id":"CVE-2020-28333","markdown":"https://insights.sbomify.com/CVE-2020-28333/index.md","name":"CVE-2020-28333","record":{"aliases":["GHSA-c8j9-wpjx-gc58"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Barco wePresent device","requires_auth":"none","summary":"Attackers can bypass authentication on Barco wePresent devices by stealing session tokens exposed in URLs, gaining unauthorized access to the web interface.","user_interaction":"not_required","vuln_class":"auth_bypass"},"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-287","name":"Improper Authentication"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Barco wePresent WiPG-1600W devices allow Authentication Bypass. Affected Version(s): 2.5.1.8. The Barco wePresent WiPG-1600W web interface does not use session cookies for tracking authenticated sessions. Instead, the web interface uses a \"SEID\" token that is appended to the end of URLs in GET requests. Thus the \"SEID\" would be exposed in web proxy logs and browser history. An attacker that is able to capture the \"SEID\" and originate requests from the same IP address (via a NAT device or web proxy) would be able to access the user interface of the device without having to know the credentials.","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":"Auth bypass in n/a","id":"CVE-2020-28333","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2020"},"n_packages":0,"n_references":2,"next":{"headline":"Hardcoded credentials in n/a","id":"CVE-2020-28334"},"packages":[],"prev":{"headline":"Other in n/a","id":"CVE-2020-28332"},"products":["n/a"],"published":"2020-11-24","related":[{"cvss_score":9.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2020-28329","kev_date_added":null,"published":"2020-11-24"},{"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":"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 bypass authentication on Barco wePresent devices by stealing session tokens exposed in URLs, gaining unauthorized access to the web interface.","url":"https://insights.sbomify.com/CVE-2020-28333/"}