# CVE-2016-10369: Other in n/a

> Local attackers can cause denial of service or bypass access controls in LX Terminal by exploiting insecure socket file handling in /tmp.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 May 2017
- **Updated:** 16 Sep 2024
- **Also known as:** ALPINE-CVE-2016-10369, DEBIAN-CVE-2016-10369, DLA-935-1, GHSA-rw5r-82jx-qr25, MGASA-2017-0138, UBUNTU-CVE-2016-10369, openSUSE-SU-2024:11031-1

## What is CVE-2016-10369?

CVE-2016-10369 is a high-severity vulnerability in n/a, published on 8 May 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

unixsocket.c in lxterminal through 0.3.0 insecurely uses /tmp for a socket file, allowing a local user to cause a denial of service (preventing terminal launch), or possibly have other impact (bypassing terminal access control).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2016-10369?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `lxterminal` | openSUSE:Tumbleweed | All versions | 0.4.0-1.5 |

Products: Lxterminal Project Lxterminal.

## How do I fix CVE-2016-10369?

Apply the vendor's patch.

## Is CVE-2016-10369 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-10369 and fix it if it is affected.

What it is: CVE-2016-10369 is a high-severity vulnerability in n/a, published on 8 May 2017. 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-2016-10369 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-2016-10369/ (Markdown: https://insights.sbomify.com/CVE-2016-10369/index.md)
```

## Sources

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

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