# CVE-2023-22495: Izanami is vulnerable to Authorization Bypass

> Attackers can bypass authentication in Izanami due to a hardcoded JWT signing secret, allowing unauthorized access and potential compromise of other instances.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jan 2023
- **Updated:** 10 Mar 2025
- **Also known as:** GHSA-9r7j-m337-792c

## What is CVE-2023-22495?

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.

### Official 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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-288 (Authentication Bypass Using an Alternate Path or Channel)

## Which versions are affected by CVE-2023-22495?

It affects 1 product.


Products: Maif Izanami.

## How do I fix CVE-2023-22495?

No fix has been published for CVE-2023-22495 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-22495 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22495 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-22495 and fix it if it is affected.

What 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22495 exists.

Affected product: MAIF izanami. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-22495/ (Markdown: https://insights.sbomify.com/CVE-2023-22495/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-22495
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-22495
- OSV: https://osv.dev/vulnerability/CVE-2023-22495

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-22495/
Summaries are generated and may contain mistakes; the official description above is the record.