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

> Attackers can extract client secrets to obtain channel access tokens and send unauthorized broadcast messages via the Line application.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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:** 24 Oct 2023
- **Updated:** 12 Sep 2024
- **Also known as:** GHSA-m3cj-392g-3vvg

## What is CVE-2023-39739?

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

### Official description

The leakage of the client secret in REGINA SWEETS&BAKERY Line 13.6.1 allows attackers to obtain the channel access token and send crafted broadcast messages.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Linecorp Regina Sweets\&bakery.

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

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

## Is CVE-2023-39739 being exploited?

There is no known exploitation of CVE-2023-39739 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-39739 is a high-severity vulnerability in n/a, published on 24 Oct 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-39739 in the wild and no public exploit code.

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-39739/ (Markdown: https://insights.sbomify.com/CVE-2023-39739/index.md)
```

## Sources

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

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