CVE-2015-5784 : Détail

Le modèle EPSS produit un score de probabilité compris entre 0 et 1 (0 et 100 %). Plus la note est élevée, plus la probabilité qu'une vulnérabilité soit exploitée est grande.

Date	EPSS V0	EPSS V1	EPSS V2 (> 2022-02-04)	EPSS V3 (> 2025-03-07)	EPSS V4 (> 2025-03-17)
2022-02-06	–	–	2.11%	–	–
2022-03-20	–	–	2.11%	–	–
2022-04-03	–	–	2.11%	–	–
2022-06-26	–	–	2.11%	–	–
2022-12-25	–	–	2.11%	–	–
2023-01-01	–	–	2.11%	–	–
2023-01-08	–	–	2.79%	–	–
2023-01-29	–	–	2.79%	–	–
2023-03-12	–	–	–	0.26%	–
2023-04-30	–	–	–	0.26%	–
2023-10-01	–	–	–	0.26%	–
2024-02-11	–	–	–	0.26%	–
2024-04-07	–	–	–	0.26%	–
2024-06-02	–	–	–	0.36%	–
2024-06-09	–	–	–	0.27%	–
2024-07-28	–	–	–	0.26%	–
2024-08-11	–	–	–	0.26%	–
2024-09-15	–	–	–	0.38%	–
2024-11-24	–	–	–	0.38%	–
2024-12-22	–	–	–	0.75%	–
2025-01-19	–	–	–	0.75%	–
2025-03-18	–	–	–	–	27.89%
2025-03-18	–	–	–	–	27.89,%

Le percentile est utilisé pour classer les CVE en fonction de leur score EPSS. Par exemple, une CVE dans le 95e percentile selon son score EPSS est plus susceptible d'être exploitée que 95 % des autres CVE. Ainsi, le percentile sert à comparer le score EPSS d'une CVE par rapport à d'autres CVE.

Date	Percentile
2022-02-06	57%
2022-03-20	58%
2022-04-03	78%
2022-06-26	79%
2022-12-25	8%
2023-01-01	79%
2023-01-08	82%
2023-01-29	83%
2023-03-12	62%
2023-04-30	63%
2023-10-01	64%
2024-02-11	65%
2024-04-07	66%
2024-06-02	72%
2024-06-09	68%
2024-07-28	66%
2024-08-11	67%
2024-09-15	73%
2024-11-24	74%
2024-12-22	81%
2025-01-19	81%
2025-03-18	96%
2025-03-18	96%

Source: https://code.google.com/p/google-security-research/issues/detail?id=477 Install.framework has a suid root binary here: /System/Library/PrivateFrameworks/Install.framework/Resources/runner This binary vends the IFInstallRunner Distributed Object, which has the following method: [IFInstallRunner makeReceiptDirAt:asRoot:] If you pass 1 for asRoot, then this code will treat the makeReceiptDirAt string as a path and make two directories (Library/Receipts) below it. At first glance this code looks immediately racy and no doubt we could play some symlink tricks to get arbitrary directories created, but, on second glance, we can do a lot more! This code is using distributed objects which is a "transparent" IPC mechanism: what this means in practise is that not only can I call methods on the IFInstallRunner object running in the suid root process, but I can also pass it objects from my process; when the suid root process then tries to call methods on those object this will actually result in callbacks into my process :) In this case rather than just passing an NSString as the makeReceiptDirAt parameter I create and pass an instance of my own class "InitialPathObject" which behaves a bit like a string but gives me complete control over its behaviour from my process. By creating a couple of this custom classes and implementing various methods we can reach calls to mkdir, chown and unlink with euid == 0. We can completely control the string passed to mkdir and unlink. In the chown case the code will chown our controlled path to root:admin; regular os x users are members of the admin group which means that this will give the user access to files which previously belonged to a different group. To hit the three actions (mkdir, chown and unlink) with controlled arguments we need to override various combinations of selectors and fail at the right points: InitialPathObject = the object we pass to the makeReceiptDirAt selector overrides: - stringByAppendingPathComponent * will be called twice: * first time: return an NSString* pointing to a non-existant file * second time: return SecondFakeStringObject SecondFakeStringObject = returned by the second call to stringByAppendingPathComponent overrides: - length * will be called by the NSFileManager? * return length of path to non-existant file - getCharacters: * will be called by the NSFileManager? * return character of the non-existant file path - fileSystemRepresentation * for MKDIR: * first time: return char* of the target path * second time: return char* to non-existant file * third time: return char* to non-existant file * for CHOWN: * first time: return char* of temporary directory to create and ignore * second time: return char* of target path * for UNLINK: * first time: return char* of temporary directory to create and ignore * second time: return char* to non-existant file * third time: return char* to path to unlink - stringByAppendingPathComponent: * for MKDIR: * not called * for CHOWN: * return NSString* pointing to file which does exist // to bail out before creating /Receipts * for UNLINK * not called build: clang -o as_root_okay_then_poc as_root_okay_then_poc.m -framework Foundation run: ./as_root_okay_then_poc MKDIR|CHOWN|UNLINK <target> note that this will create some root-owned temporary directories in /tmp which will need to be manually cleaned up Proof of Concept: https://gitlab.com/exploit-database/exploitdb-bin-sploits/-/raw/main/bin-sploits/38137.zip