# CVE-2024-6294: udn News App - Sensitive Information Exposure

> Attackers can retrieve user session tokens from logcat files to hijack accounts and access services.

- **Severity:** Low 3.9 (`CVSS:3.1/AV:P/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-cv9m-q4c9-4vr9

## What is CVE-2024-6294?

CVE-2024-6294 is a low-severity vulnerability in udn News App, published on 25 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

udn News Android APP stores the user session in logcat file when user log into the APP. A malicious APP or an attacker with physical access to the Android device can retrieve this session and use it to log into the news APP and other services provided by udn.

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

## Which versions are affected by CVE-2024-6294?


## How do I fix CVE-2024-6294?

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

## Is CVE-2024-6294 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-6294 and fix it if it is affected.

What it is: CVE-2024-6294 is a low-severity vulnerability in udn News App, published on 25 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-6294 in the wild and no public exploit code.

Affected product: udn News App. 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-2024-6294/ (Markdown: https://insights.sbomify.com/CVE-2024-6294/index.md)
```

## Sources

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

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