{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-41553 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-41553 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-41553 is a critical authentication bypass vulnerability in n/a, published on 5 Oct 2021. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2021-41553 and fix it if it is affected.\n\nWhat it is: CVE-2021-41553 is a critical authentication bypass vulnerability in n/a, published on 5 Oct 2021. 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-2021-41553 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-2021-41553/ (Markdown: https://insights.sbomify.com/CVE-2021-41553/index.md)","id":"CVE-2021-41553","markdown":"https://insights.sbomify.com/CVE-2021-41553/index.md","name":"CVE-2021-41553","record":{"aliases":["GHSA-wfm6-393x-c6r9"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"ARCHIBUS Web Central","requires_auth":"none","summary":"Attackers can hijack user sessions by setting a known JSESSIONID before login, allowing unauthorized access to the ARCHIBUS Web Central application.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"web_central","vendor":"archibus"}],"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-384","name":"Session Fixation"}],"description":"In ARCHIBUS Web Central 21.3.3.815 (a version from 2014), the Web Application in /archibus/login.axvw assign a session token that could be already in use by another user. It was therefore possible to access the application through a user whose credentials were not known, without any attempt by the testers to modify the application logic. It is also possible to set the value of the session token, client-side, simply by making an unauthenticated GET Request to the Home Page and adding an arbitrary value to the JSESSIONID field. The application, following the login, does not assign a new token, continuing to keep the inserted one, as the identifier of the entire session. This is fixed in all recent versions, such as version 26. NOTE: This vulnerability only affects products that are no longer supported by the maintainer. Version 21.3 was officially de-supported by the end of 2020","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-2021-41553","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2021"},"n_packages":0,"n_references":1,"next":{"headline":"Missing authorization in n/a","id":"CVE-2021-41554"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2021-41552"},"products":["n/a"],"published":"2021-10-05","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-28862","kev_date_added":null,"published":"2022-05-25"},{"cvss_score":8.8,"headline":"Missing authorization in n/a","id":"CVE-2021-41554","kev_date_added":null,"published":"2021-10-05"},{"cvss_score":6.5,"headline":"SQL injection in n/a","id":"CVE-2022-45165","kev_date_added":null,"published":"2023-01-10"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2021-41555","kev_date_added":null,"published":"2021-10-05"}],"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 hijack user sessions by setting a known JSESSIONID before login, allowing unauthorized access to the ARCHIBUS Web Central application.","url":"https://insights.sbomify.com/CVE-2021-41553/"}