{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2021-38618 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2021-38618 yet. Limit exposure of the affected software until one is available.","what":"CVE-2021-38618 is a high-severity authentication bypass vulnerability in n/a, published on 4 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-38618 and fix it if it is affected.\n\nWhat it is: CVE-2021-38618 is a high-severity authentication bypass vulnerability in n/a, published on 4 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-38618 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-38618/ (Markdown: https://insights.sbomify.com/CVE-2021-38618/index.md)","id":"CVE-2021-38618","markdown":"https://insights.sbomify.com/CVE-2021-38618/index.md","name":"CVE-2021-38618","record":{"aliases":["GHSA-7g52-j5fp-g582"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Workforce Management","requires_auth":"none","summary":"An authentication bypass in GFOS Workforce Management allows attackers to access accounts by exploiting JSESSIONID mismanagement, requiring only the username.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"workforce_management","vendor":"gfos"}],"cvss":{"score":7.4,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:H/AV:N/A:N/C:H/I:H/PR:N/S:U/UI:N","version":"3.1"},"cwes":[],"description":"In GFOS Workforce Management 4.8.272.1, the login page of application is prone to authentication bypass, allowing anyone (who knows a user's credentials except the password) to get access to an account. This occurs because of JSESSIONID mismanagement.","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-38618","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2021"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2021-38619"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2021-38617"},"products":["n/a"],"published":"2021-10-04","related":[],"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":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2025-05-30","vendors":["n/a"]},"summary":"An authentication bypass in GFOS Workforce Management allows attackers to access accounts by exploiting JSESSIONID mismanagement, requiring only the username.","url":"https://insights.sbomify.com/CVE-2021-38618/"}