# CVE-2022-48257: Information disclosure in n/a

> Predictable log file names in /tmp allow attackers to read sensitive information from Eternal Terminal logs.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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:** Yes
- **Published:** 13 Jan 2023
- **Updated:** 4 Nov 2025
- **Also known as:** GHSA-9526-g73c-89rr

## What is CVE-2022-48257?

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

### Official description

In Eternal Terminal 6.2.1, etserver and etclient have predictable logfile names in /tmp.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

## Which versions are affected by CVE-2022-48257?

It affects 1 product.


Products: Eternal Terminal Project Eternal Terminal.

## How do I fix CVE-2022-48257?

Apply the vendor's patch.

## Is CVE-2022-48257 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-24949](https://insights.sbomify.com/CVE-2022-24949/): Privilege escalation in Eternal Terminal (high 7.5)
- [CVE-2022-24950](https://insights.sbomify.com/CVE-2022-24950/): Race condition in Eternal Terminal (high 7.5)
- [CVE-2022-24951](https://insights.sbomify.com/CVE-2022-24951/): Race condition in Eternal Terminal (high 7.0)
- [CVE-2022-24952](https://insights.sbomify.com/CVE-2022-24952/): Several denial of service vulnerabilities exist in Eternal Terminal prior to version 6.2.0, including a DoS triggered remotely by an invalid (medium 6.5)
- [CVE-2023-23558](https://insights.sbomify.com/CVE-2023-23558/): Path traversal in n/a (medium 6.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-48257 and fix it if it is affected.

What it is: CVE-2022-48257 is a medium-severity vulnerability in n/a, published on 13 Jan 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-2022-48257 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-2022-48257/ (Markdown: https://insights.sbomify.com/CVE-2022-48257/index.md)
```

## Sources

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

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