CVE-2019-15325 In GalliumOS 3.0, CONFIG_SECURITY_YAMA is disabled but /etc/sysctl.d/10-ptrace.conf tries to set /proc/sys/kernel/yama/ptrace_scope to 1, wh
High 7.5
Published
Updated
Check this codebase for CVE-2019-15325 and fix it if it is affected.
What it is: CVE-2019-15325 is a high-severity vulnerability in n/a, published on 22 Aug 2019.
Exploitation: There is no known exploitation of CVE-2019-15325 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-15325/ (Markdown: https://insights.sbomify.com/CVE-2019-15325/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-2019-15325?
CVE-2019-15325 is a high-severity vulnerability in n/a, published on 22 Aug 2019.
Official description
In GalliumOS 3.0, CONFIG_SECURITY_YAMA is disabled but /etc/sysctl.d/10-ptrace.conf tries to set /proc/sys/kernel/yama/ptrace_scope to 1, which might increase risk because of the appearance that a protection mechanism is present when actually it is not.
Which versions are affected by CVE-2019-15325?
It affects 1 product.
Products include Galliumos Galliumos.
How do I fix CVE-2019-15325?
No fix has been published for CVE-2019-15325 yet. Limit exposure of the affected software until one is available.
Is CVE-2019-15325 being exploited?
There is no known exploitation of CVE-2019-15325 in the wild and no public exploit code.
Sources
Also known as GHSA-q9qm-mg3c-p65c.