CVE-2010-4210
published 2010-11-22CVE-2010-4210: The pfs_getextattr function in FreeBSD 7.x before 7.3-RELEASE and 8.x before 8.0-RC1 unlocks a mutex that was not previously locked, which allows local users…
PriorityP434high7.8CVSS 3.1
AVLACLPRNUIRSUCHIHAH
EXPLOIT
EPSS
1.13%
62.4th percentile
The pfs_getextattr function in FreeBSD 7.x before 7.3-RELEASE and 8.x before 8.0-RC1 unlocks a mutex that was not previously locked, which allows local users to cause a denial of service (kernel panic), overwrite arbitrary memory locations, and possibly execute arbitrary code via vectors related to opening a file on a file system that uses pseudofs.
Affected
2 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| freebsd | freebsd | — | — |
| freebsd | freebsd | >= 7.0 < 7.3 | 7.3 |
CVSS provenance
nvdv3.17.8HIGHCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
nvdv2.07.2HIGHAV:L/AC:L/Au:N/C:C/I:C/A:C
CVEs like this are exactly what “Exploited This Week” covers.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-78h7-v2wq-qphc: The pfs_getextattr function in FreeBSD 7
ghsa_unreviewed·2022-05-17
CVE-2010-4210 [HIGH] CWE-667 GHSA-78h7-v2wq-qphc: The pfs_getextattr function in FreeBSD 7
The pfs_getextattr function in FreeBSD 7.x before 7.3-RELEASE and 8.x before 8.0-RC1 unlocks a mutex that was not previously locked, which allows local users to cause a denial of service (kernel panic), overwrite arbitrary memory locations, and possibly execute arbitrary code via vectors related to opening a file on a file system that uses pseudofs.
BSD
FreeBSD-SA-10:09.pseudofs: Spurious mutex unlock
bsd_advisories·2010-11-10·CVSS 7.8
CVE-2010-4210 [HIGH] FreeBSD-SA-10:09.pseudofs: Spurious mutex unlock
FreeBSD-SA-10:09.pseudofs Security Advisory
The FreeBSD Project
Topic: Spurious mutex unlock
Category: core
Module: pseudofs
Announced: 2010-11-10
Credits: Przemyslaw Frasunek
Affects: FreeBSD 7.x prior to 7.3-RELEASE, 8.x prior to 8.0-RC1
Corrected: 2009-09-05 13:10:54 UTC (RELENG_8, 8.0-RC1)
2009-09-05 13:31:16 UTC (RELENG_7, 7.2-STABLE)
2010-11-10 23:36:13 UTC (RELENG_7_1, 7.1-RELEASE-p15)
CVE Name: CVE-2010-4210
For general information regarding FreeBSD Security Advisories,
including descriptions of the fields above, security branches, and the
following sections, please visit .
I. Background
pseudofs offers an abstract API for pseudo file systems which is utilized by
procfs(5) and linprocfs(5). It provides generic file system services such
as ACLs, extended attributes which interf
No detection rules found.
No writeups or analysis indexed.
CWE
Unlock of a Resource that is not Locked
mitre_cwe·CVSS 5.5
[MEDIUM] CWE-832 Unlock of a Resource that is not Locked
CWE-832: Unlock of a Resource that is not Locked
The product attempts to unlock a resource that is not locked.
Depending on the locking functionality, an unlock of a non-locked resource might cause memory corruption or other modification to the resource (or its associated metadata that is used for tracking locks).
Modes of Introduction:
Phase: Implementation
Common Consequences:
Scope: Integrity, Confidentiality, Availability, Other. Impact: DoS: Crash, Exit, or Restart, Execute Unauthorized Code or Commands, Modify Memory, Other. Depending on the locking being used, an unlock operation might not have any adverse effects. When effects exist, the most common consequence will be a corruption of the state of the product, possibly leading to a crash or exit; depending on the implementation
CWE
Improper Locking
mitre_cwe
CWE-667 Improper Locking
CWE-667: Improper Locking
The product does not properly acquire or release a lock on a resource, leading to unexpected resource state changes and behaviors.
Locking is a type of synchronization behavior that ensures that multiple independently-operating processes or threads do not interfere with each other when accessing the same resource. All processes/threads are expected to follow the same steps for locking. If these steps are not followed precisely - or if no locking is done at all - then another process/thread could modify the shared resource in a way that is not visible or predictable to the original process. This can lead to data or memory corruption, denial of service, etc.
Modes of Introduction:
Phase: Architecture and Design
Phase: Implementation
Common Consequences:
Scope: A
http://secunia.com/advisories/42200http://security.FreeBSD.org/advisories/FreeBSD-SA-10:09.pseudofs.aschttp://www.securitytracker.com/id?1024724http://www.vupen.com/english/advisories/2010/2956https://exchange.xforce.ibmcloud.com/vulnerabilities/63218https://www.exploit-db.com/exploits/15206/http://secunia.com/advisories/42200http://security.FreeBSD.org/advisories/FreeBSD-SA-10:09.pseudofs.aschttp://www.securitytracker.com/id?1024724http://www.vupen.com/english/advisories/2010/2956https://exchange.xforce.ibmcloud.com/vulnerabilities/63218https://www.exploit-db.com/exploits/15206/
2010-11-22
Published