CVE-2022-25643
CRITICALCVSS 9.8/10EPSS 2.06%
Last modified
CVE-2022-25643 is a critical-severity vulnerability rated 9.8/10 on the CVSS scale. seatd-launch in seatd 0.6.x before 0.6.4 allows removing files with escalated privileges when installed setuid root. The attack vector is a user-supplied socket pathname.. EPSS estimates a 2.06% chance of exploitation in the next 30 days.
Description
seatd-launch in seatd 0.6.x before 0.6.4 allows removing files with escalated privileges when installed setuid root. The attack vector is a user-supplied socket pathname.
Metrics
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Weakness Enumeration
Affected Software
| Vendor | Product | Versions |
|---|---|---|
| Seatd Project | Seatd | >= 0.6.0, < 0.6.4 |
References
- https://github.com/kennylevinsen/seatd/compare/0.6.3...0.6.4Release Notes, Third Party Advisory
- https://github.com/kennylevinsen/seatd/tagsThird Party Advisory
- https://github.com/kennylevinsen/seatd/compare/0.6.3...0.6.4Release Notes, Third Party Advisory
- https://github.com/kennylevinsen/seatd/tagsThird Party Advisory
Timeline
- Published
- Last Modified
- Status
- Modified
Frequently Asked Questions
What is CVE-2022-25643?
seatd-launch in seatd 0.6.x before 0.6.4 allows removing files with escalated privileges when installed setuid root. The attack vector is a user-supplied socket pathname.
How severe is CVE-2022-25643?
CVE-2022-25643 has a CVSS score of 9.8/10 (CRITICAL severity). The EPSS model estimates a 2.06% probability of exploitation in the next 30 days.
How do I fix CVE-2022-25643?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2022
- CVE-2022-25636net/netfilter/nf_dup_netdev.c in the Linux kernel 5.4 throug…7.8
- CVE-2022-25638In wolfSSL before 5.2.0, certificate validation may be bypas…6.5
- CVE-2022-2564Prototype Pollution in GitHub repository automattic/mongoose…9.8
- CVE-2022-25640In wolfSSL before 5.2.0, a TLS 1.3 server cannot properly en…7.5
- CVE-2022-25641Foxit PDF Reader before 11.2.2 and PDF Editor before 11.2.2,…5.5
- CVE-2022-25642Obyte (formerly Byteball) Wallet before 3.4.1 allows XSS. A …6.1
- CVE-2022-25644All versions of package @pendo324/get-process-by-name are vu…9.8
- CVE-2022-25645All versions of package dset are vulnerable to Prototype Pol…8.1
- CVE-2022-25646All versions of package x-data-spreadsheet are vulnerable to…6.1
- CVE-2022-25647The package com.google.code.gson:gson before 2.8.9 are vulne…7.5
- CVE-2022-25648The package git before 1.11.0 are vulnerable to Command Inje…9.8
- CVE-2022-25649Multiple Improper Access Control vulnerabilities in StoreApp…8.8
Are you affected by CVE-2022-25643?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST