CVE-2008-2018 : 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	–	–	4.19%	–	–
2022-04-03	–	–	4.19%	–	–
2022-07-17	–	–	4.19%	–	–
2023-03-12	–	–	–	0.43%	–
2023-04-02	–	–	–	0.43%	–
2023-04-09	–	–	–	0.54%	–
2023-09-10	–	–	–	0.54%	–
2023-11-12	–	–	–	0.49%	–
2023-12-24	–	–	–	0.49%	–
2024-02-11	–	–	–	0.49%	–
2024-02-25	–	–	–	0.51%	–
2024-06-02	–	–	–	0.51%	–
2024-08-25	–	–	–	0.5%	–
2024-09-22	–	–	–	0.5%	–
2024-09-29	–	–	–	0.5%	–
2024-10-06	–	–	–	0.46%	–
2024-12-22	–	–	–	0.46%	–
2025-03-09	–	–	–	0.52%	–
2025-01-19	–	–	–	0.46%	–
2025-03-09	–	–	–	0.52%	–
2025-03-18	–	–	–	–	1.62%
2025-03-30	–	–	–	–	1.69%
2025-04-30	–	–	–	–	1.89%
2025-04-30	–	–	–	–	1.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	7%
2022-04-03	86%
2022-07-17	87%
2023-03-12	7%
2023-04-02	71%
2023-04-09	74%
2023-09-10	75%
2023-11-12	73%
2023-12-24	74%
2024-02-11	75%
2024-02-25	76%
2024-06-02	77%
2024-08-25	77%
2024-09-22	76%
2024-09-29	77%
2024-10-06	76%
2024-12-22	75%
2025-03-09	77%
2025-01-19	75%
2025-03-09	77%
2025-03-18	81%
2025-03-30	81%
2025-04-30	82%
2025-04-30	82%

-------------------------------------------------------- PHPizabi v0.848b C1 HFP3 database information exposure -------------------------------------------------------- * I would like to state that I am in no way responsible for how this information is used. It is just that, information and is provided for informational purposes only.* An exploit exists in PHPizabi that allows a user using a specially crafted post to disclose user credentials as well as any other information within the database. Using the following format in a post to a users profile will disclose the corresponding field from that users entry in the database. FORMAT: {user.DATABASEFIELD} The breakdown: template.class.php function AssignUser lines 104-108 if (is_array($user)) { foreach ($user as $code => $value) { Vulnerable code ----------> $this->Buffer = str_replace("{user.".$code."}", $value, $this->Buffer); } } What happens here is that as an array of database fields is processed, if {user.DATABASEFIELD} is found in the buffer it is overwritten with the corresponding value from the database. The buffer being processed is going to be output as the page. See where this is going? :) So the basic process is as this. Register on PHPizabi site, post a "comment" on the users profile whos credentials you want to obtain ie the admin. Being like so {user.password} When viewing the profile, click the comments tab and then click "View all comments". This will disclose the md5 hashed password from the database. Note this could work on older versions of the software too. Also any valid database field can be substituted for password in the above statement. -------------------------------------------------------- by: YOUCODE --- icode00@gmail.com -------------------------------------------------------- # milw0rm.com [2008-04-26]