# CVE-2024-6295: udn News App - Insecure Data Storage

> Attackers with physical access or malicious apps can steal unencrypted session data from the udn News Android app to hijack user accounts.

- **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-628q-5gqp-mr86

## What is CVE-2024-6295?

CVE-2024-6295 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 unencrypted user session in the local database when user log into the application. 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-922 (Insecure Storage of Sensitive Information)

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


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

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

## Is CVE-2024-6295 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-6295 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-6295 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-6295/ (Markdown: https://insights.sbomify.com/CVE-2024-6295/index.md)
```

## Sources

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

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