{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2022-46382 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2022-46382 yet. Limit exposure of the affected software until one is available.","what":"CVE-2022-46382 is a high-severity authentication bypass vulnerability in n/a, published on 6 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2022-46382 and fix it if it is affected.\n\nWhat it is: CVE-2022-46382 is a high-severity authentication bypass vulnerability in n/a, published on 6 Dec 2022. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2022-46382 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-2022-46382/ (Markdown: https://insights.sbomify.com/CVE-2022-46382/index.md)","id":"CVE-2022-46382","markdown":"https://insights.sbomify.com/CVE-2022-46382/index.md","name":"CVE-2022-46382","record":{"aliases":["GHSA-qf5h-2qwh-9v97"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Digital Rebar","requires_auth":"low_privilege","summary":"Deleted users retain valid authentication tokens, allowing them to perform unauthorized actions within Digital Rebar.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"digital_rebar","vendor":"rackn"}],"cvss":{"score":8.8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-276","name":"Incorrect Default Permissions"}],"description":"RackN Digital Rebar through 4.6.14, 4.7 through 4.7.22, 4.8 through 4.8.5, 4.9 through 4.9.12, and 4.10 through 4.10.8 has Insecure Permissions. After signing into Digital Rebar, users are issued authentication tokens tied to their account to perform actions within Digital Rebar. During the validation process of these tokens, Digital Rebar did not check if the user account still exists. Deleted Digital Rebar users could still use their tokens to perform actions within Digital Rebar.","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-2022-46382","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2022"},"n_packages":0,"n_references":1,"next":{"headline":"Information disclosure in n/a","id":"CVE-2022-46383"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2022-46381"},"products":["n/a"],"published":"2022-12-06","related":[{"cvss_score":9.8,"headline":"Information disclosure in n/a","id":"CVE-2022-46383","kev_date_added":null,"published":"2022-12-06"}],"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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-23","vendors":["n/a"]},"summary":"Deleted users retain valid authentication tokens, allowing them to perform unauthorized actions within Digital Rebar.","url":"https://insights.sbomify.com/CVE-2022-46382/"}