CVE-1999-1413 Solaris 2.4 before kernel jumbo patch -35 allows set-gid programs to dump core even if the real user id is not in the set-gid group, which a
Medium 4.6
Published
Updated
Check this codebase for CVE-1999-1413 and fix it if it is affected.
What it is: CVE-1999-1413 is a medium-severity vulnerability in Sun Solaris, published on 12 Sep 2001.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-1999-1413 exists.
Affected product: Sun Solaris. 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-1999-1413/ (Markdown: https://insights.sbomify.com/CVE-1999-1413/index.md)
- Exploited in the wild
- Not known
- Fix
- None listed
What is CVE-1999-1413?
CVE-1999-1413 is a medium-severity vulnerability in Sun Solaris, published on 12 Sep 2001.
Official description
Solaris 2.4 before kernel jumbo patch -35 allows set-gid programs to dump core even if the real user id is not in the set-gid group, which allows local users to overwrite or create files at higher privileges by causing a core dump, e.g. through dmesg.
Which versions are affected by CVE-1999-1413?
It affects 2 products.
Products include Sun Solaris, Sun Sunos.
How do I fix CVE-1999-1413?
No fix has been published for CVE-1999-1413 yet. Limit exposure of the affected software until one is available.
Is CVE-1999-1413 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-1999-1413 exists.
Public exploit code: 1 Exploit-DB entry.
Other vulnerabilities in Sun Solaris
Sources
Also known as GHSA-6v6p-c65q-8x22.