# CVE-2023-31821: Information disclosure in n/a

> Remote attackers can access sensitive information via the channel access token in the ALBIS miniapp function.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2023
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-r9w4-5f8x-9rmm

## What is CVE-2023-31821?

CVE-2023-31821 is a high-severity vulnerability in n/a, published on 13 Jul 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue found in ALBIS Co. ALBIS v.13.6.1 allows a remote attacker to gain access to sensitive information via the channel access token in the miniapp ALBIS function.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

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

It affects 1 product.


Products: Albis Albis.

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

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

## Is CVE-2023-31821 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2023-31821 is a high-severity vulnerability in n/a, published on 13 Jul 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-31821 exists.

Affected product: n/a. 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-31821/ (Markdown: https://insights.sbomify.com/CVE-2023-31821/index.md)
```

## Sources

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

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