# CVE-2019-12779: Path traversal in n/a

> Local attackers can overwrite arbitrary files via symlink attacks due to predictable filenames in libqb shared memory operations.

- **Severity:** High 7.1 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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:** 7 Jun 2019
- **Updated:** 4 Aug 2024
- **Also known as:** CVE-2019-10148, DEBIAN-CVE-2019-12779, GHSA-wc62-h53h-g8qf, MGASA-2020-0048, OESA-2021-1141, RHSA-2019:3610, RHSA-2020:1189, SUSE-SU-2019:1791-1, SUSE-SU-2019:1806-1, SUSE-SU-2019:1812-1, UBUNTU-CVE-2019-12779, openSUSE-SU-2019:1718-1, openSUSE-SU-2019:1752-1, openSUSE-SU-2019:1891-1, openSUSE-SU-2024:10974-1

## What is CVE-2019-12779?

CVE-2019-12779 is a high-severity path traversal vulnerability in n/a, published on 7 Jun 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

libqb before 1.0.5 allows local users to overwrite arbitrary files via a symlink attack, because it uses predictable filenames (under /dev/shm and /tmp) without O_EXCL.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2019-12779?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libqb` | Red Hat:enterprise_linux:7::client | All versions | 0:1.0.1-9.el7 |
| `libqb-debuginfo` | Red Hat:enterprise_linux:7::client | All versions | 0:1.0.1-9.el7 |
| `libqb-devel` | Red Hat:enterprise_linux:7::client | All versions | 0:1.0.1-9.el7 |
| `libqb` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.0.1-9.el7 |
| `libqb-debuginfo` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.0.1-9.el7 |
| `libqb-devel` | Red Hat:enterprise_linux:7::computenode | All versions | 0:1.0.1-9.el7 |
| `libqb` | Red Hat:enterprise_linux:7::server | All versions | 0:1.0.1-9.el7 |
| `libqb-debuginfo` | Red Hat:enterprise_linux:7::server | All versions | 0:1.0.1-9.el7 |
| `libqb-devel` | Red Hat:enterprise_linux:7::server | All versions | 0:1.0.1-9.el7 |
| `libqb` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.0.1-9.el7 |
| `libqb-debuginfo` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.0.1-9.el7 |
| `libqb-devel` | Red Hat:enterprise_linux:7::workstation | All versions | 0:1.0.1-9.el7 |
| `libqb` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.3-10.el8 |
| `libqb-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.3-10.el8 |
| `libqb-debugsource` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.3-10.el8 |
| `libqb-devel` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.3-10.el8 |
| `libqb-tests-debuginfo` | Red Hat:enterprise_linux:8::baseos | All versions | 0:1.0.3-10.el8 |
| `libdlm` | SUSE:Linux Enterprise High Availability Extension 12 SP3 | All versions | 4.0.7-3.3.2 |
| `libqb` | SUSE:Linux Enterprise High Availability Extension 12 SP3 | All versions | 1.0.3+20171226.6d62b64-4.3.1 |
| `libdlm` | SUSE:Linux Enterprise High Availability Extension 12 SP4 | All versions | 4.0.7-3.3.2 |
| `libqb` | SUSE:Linux Enterprise High Availability Extension 12 SP4 | All versions | 1.0.3+20171226.6d62b64-4.3.1 |
| `libqb` | SUSE:Linux Enterprise High Availability Extension 15 | All versions | 1.0.3+20171226.6d62b64-3.3.1 |
| `libqb` | SUSE:Linux Enterprise High Availability Extension 15 SP1 | All versions | 1.0.3+20190326.a521604-3.3.1 |
| `libdlm` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 4.0.7-3.3.2 |
| `libqb` | SUSE:Linux Enterprise Software Development Kit 12 SP4 | All versions | 1.0.3+20171226.6d62b64-4.3.1 |
| `libqb` | SUSE:Package Hub 15 SP1 | All versions | 1.0.3+20190326.a521604-bp151.2.3.1 |
| `libqb` | openSUSE:Leap 15.0 | All versions | 1.0.3+20171226.6d62b64-lp150.2.3.1 |
| `libqb` | openSUSE:Leap 15.1 | All versions | 1.0.3+20190326.a521604-lp151.2.3.1 |

Products: Clusterlabs Libqb.

## How do I fix CVE-2019-12779?

Upgrade to a fixed version.

## Is CVE-2019-12779 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-39976](https://insights.sbomify.com/CVE-2023-39976/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-12779 and fix it if it is affected.

What it is: CVE-2019-12779 is a high-severity path traversal vulnerability in n/a, published on 7 Jun 2019. 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-2019-12779 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-2019-12779/ (Markdown: https://insights.sbomify.com/CVE-2019-12779/index.md)
```

## Sources

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

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