{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22495 exists.","fix":"No fix has been published for CVE-2023-22495 yet. Limit exposure of the affected software until one is available.","what":"CVE-2023-22495 is a critical vulnerability in MAIF izanami, published on 14 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2023-22495 and fix it if it is affected.\n\nWhat it is: CVE-2023-22495 is a critical vulnerability in MAIF izanami, published on 14 Jan 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22495 exists.\n\nAffected product: MAIF izanami. 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-2023-22495/ (Markdown: https://insights.sbomify.com/CVE-2023-22495/index.md)","id":"CVE-2023-22495","markdown":"https://insights.sbomify.com/CVE-2023-22495/index.md","name":"CVE-2023-22495","record":{"aliases":["GHSA-9r7j-m337-792c"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"Izanami configuration service","requires_auth":"none","summary":"Attackers can bypass authentication in Izanami due to a hardcoded JWT signing secret, allowing unauthorized access and potential compromise of other instances.","user_interaction":"not_required","vuln_class":"hardcoded_credentials"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"izanami","vendor":"maif"}],"cvss":{"score":9.8,"severity":"critical","source":"cna","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-798","name":"Use of Hard-coded Credentials"},{"id":"CWE-288","name":"Authentication Bypass Using an Alternate Path or Channel"}],"description":"Izanami is a shared configuration service well-suited for micro-service architecture implementation. Attackers can bypass the authentication in this application when deployed using the official Docker image. Because a hard coded secret is used to sign the authentication token (JWT), an attacker could compromise another instance of Izanami. This issue has been patched in version 1.11.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Izanami is vulnerable to Authorization Bypass","id":"CVE-2023-22495","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"hardcoded_credentials","year":"2023"},"n_packages":0,"n_references":2,"next":{"headline":"Netdata vulnerable to command injection","id":"CVE-2023-22496"},"packages":[],"prev":{"headline":"RSSHub is vulnerable to SSRF (Server-Side Request Forgery)","id":"CVE-2023-22493"},"products":["izanami"],"published":"2023-01-14","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":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-03-10","vendors":["MAIF"]},"summary":"Attackers can bypass authentication in Izanami due to a hardcoded JWT signing secret, allowing unauthorized access and potential compromise of other instances.","url":"https://insights.sbomify.com/CVE-2023-22495/"}