{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2020-26172 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2020-26172 yet. Limit exposure of the affected software until one is available.","what":"CVE-2020-26172 is a medium-severity authentication bypass vulnerability in n/a, published on 18 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-26172 and fix it if it is affected.\n\nWhat it is: CVE-2020-26172 is a medium-severity authentication bypass vulnerability in n/a, published on 18 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-26172 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-26172/ (Markdown: https://insights.sbomify.com/CVE-2020-26172/index.md)","id":"CVE-2020-26172","markdown":"https://insights.sbomify.com/CVE-2020-26172/index.md","name":"CVE-2020-26172","record":{"aliases":["GHSA-jj37-qmmg-fmgp"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Business Workflow","requires_auth":"none","summary":"Attackers can reuse static JWT tokens to hijack active sessions due to missing expiration and unique identifiers in tangro Business Workflow.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"business_workflow","vendor":"tangro"}],"cvss":{"score":4.2,"severity":"medium","source":"cna","vector":"CVSS:3.1/AC:H/AV:N/A:N/C:L/I:L/PR:N/S:U/UI:R","version":"3.1"},"cwes":[{"id":"CWE-294","name":"Authentication Bypass by Capture-replay"}],"description":"Every login in tangro Business Workflow before 1.18.1 generates the same JWT token, which allows an attacker to reuse the token when a session is active. The JWT token does not contain an expiration timestamp.","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-26172","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":"Missing authorization in n/a","id":"CVE-2020-26173"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2020-26171"},"products":["n/a"],"published":"2020-12-18","related":[{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2020-26174","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":6.5,"headline":"Missing authorization in n/a","id":"CVE-2020-26175","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2020-26178","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2020-26171","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2020-26176","kev_date_added":null,"published":"2020-12-18"},{"cvss_score":4.3,"headline":"Missing authorization in n/a","id":"CVE-2020-26177","kev_date_added":null,"published":"2020-12-18"}],"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 reuse static JWT tokens to hijack active sessions due to missing expiration and unique identifiers in tangro Business Workflow.","url":"https://insights.sbomify.com/CVE-2020-26172/"}