{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26290 in the wild and no public exploit code.","fix":"Upgrade to a fixed version.","what":"CVE-2020-26290 is a critical vulnerability in dexidp dex, published on 28 Dec 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2020-26290 and fix it if it is affected.\n\nWhat it is: CVE-2020-26290 is a critical vulnerability in dexidp dex, published on 28 Dec 2020. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2020-26290 in the wild and no public exploit code.\n\nAffected product: dexidp dex. 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-26290/ (Markdown: https://insights.sbomify.com/CVE-2020-26290/index.md)","id":"CVE-2020-26290","markdown":"https://insights.sbomify.com/CVE-2020-26290/index.md","name":"CVE-2020-26290","record":{"aliases":["openSUSE-SU-2024:10714-1"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":true,"product_category":"OpenID Connect provider","requires_auth":"none","summary":"Attackers can bypass SAML signature validation in Dex due to XML encoding flaws, allowing unauthorized access if the SAML connector is enabled.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"dex","vendor":"linuxfoundation"}],"cvss":{"score":9.3,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-347","name":"Improper Verification of Cryptographic Signature"}],"description":"Dex is a federated OpenID Connect provider written in Go. In Dex before version 2.27.0 there is a critical set of vulnerabilities which impacts users leveraging the SAML connector. The vulnerabilities enables potential signature bypass due to issues with XML encoding in the underlying Go library. The vulnerabilities have been addressed in version 2.27.0 by using the xml-roundtrip-validator from Mattermost (see related references).","ecosystems":["openSUSE:Tumbleweed"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Critical security issues in XML encoding in Dex","id":"CVE-2020-26290","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2020"},"n_packages":1,"n_references":8,"next":{"headline":"Hostname spoofing in URI.js","id":"CVE-2020-26291"},"packages":[{"ecosystem":"openSUSE:Tumbleweed","fixed":["2.28.1-1.3"],"introduced":["0"],"last_affected":[],"package":"dex-oidc","purl":"pkg:rpm/opensuse/dex-oidc\u0026distro=openSUSE%20Tumbleweed","source":"openSUSE-SU-2024:10714-1"}],"prev":{"headline":"Regular expression Denial of Service in date-and-time","id":"CVE-2020-26289"},"products":["dex"],"published":"2020-12-28","related":[{"cvss_score":9.8,"headline":"Auth bypass in dexidp/dex","id":"CVE-2020-27847","kev_date_added":null,"published":"2021-05-28"},{"cvss_score":9.3,"headline":"OAuth authorization code exposure in Dex","id":"CVE-2022-39222","kev_date_added":null,"published":"2022-10-06"},{"cvss_score":7.5,"headline":"Dex 2.37.0 is discarding TLSconfig and always serves deprecated TLS 1.0/1.1 and insecure ciphers","id":"CVE-2024-23656","kev_date_added":null,"published":"2024-01-25"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"SUSE","prefix":"openSUSE"},{"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":["dexidp"]},"summary":"Attackers can bypass SAML signature validation in Dex due to XML encoding flaws, allowing unauthorized access if the SAML connector is enabled.","url":"https://insights.sbomify.com/CVE-2020-26290/"}