{"vuid":"VU#572615","idnumber":"572615","name":"Vulnerabilities in TP-Link routers, WR710N-V1-151022 and Archer C5 V2","keywords":null,"overview":"### Overview\r\nTP-Link router WR710N-V1-151022 running firmware published 2015-10-22 and Archer-C5-V2-160201 running firmware published 2016-02-01 are susceptible to two vulnerabilities:\r\n\r\n1. A buffer overflow during HTTP Basic Authentication allowing a remote attacker to corrupt memory allocated on a heap causing denial of service or arbitrary code execution;\r\n3. A side-channel attack via a *strcmp()* function in the HTTP daemon allowing deterministic guessing of each byte of a username and password input during authentication.\r\n### Description\r\nTP-Link device WR710N-V1-151022 is a 150Mbps Wireless N Mini Pocket router, and Archer-C5-V2-160201 is a Wireless Dual Band Gigabit router. These SOHO devices are sold by TP-Link and their latest firmware available as of January 11, 2023, have two vulnerabilities. \r\n\r\n**CVE-2022-4498**\r\nWhen receiving user input during HTTP Basic Authentication mode, a crafted packet may cause a heap overflow in the *httpd* daemon. This can lead to denial of service (DoS) if the *httpd* process crashes or arbitrary remote code execution (RCE).\r\n\r\n**CVE-2022-4499**\r\nA *strcmp()* function in *httpd*, is susceptible to a side-channel attack when used to verify usename and password credentials. By measuring the response time of the vulnerable process, each byte of the username and password strings may be easier to guess.\r\n\r\n### Impact\r\nThe two different vulnerabilities have unrelated impacts. The first vulnerability is a heap-based buffer overflow that can cause a crash or allow for arbitrary remote code execution. The second vulnerability is an information disclosure issue where the function used by the *httpd* process may allow an attacker to guess each byte of a username and password deterministically.\r\n\r\n### Solution\r\nThe CERT/CC is currently unaware of a practical solution to this problem. \r\n\r\n### Acknowledgements\r\nThanks to the reporter, Jonathan Bar of Microsoft, for responsibly disclosing these issues.\r\n\r\nThis document was written by Timur Snoke.","clean_desc":null,"impact":null,"resolution":null,"workarounds":null,"sysaffected":null,"thanks":null,"author":null,"public":[],"cveids":["CVE-2022-4499","CVE-2022-4498"],"certadvisory":null,"uscerttechnicalalert":null,"datecreated":"2023-01-17T17:41:06.007421Z","publicdate":"2023-01-17T17:41:05.807853Z","datefirstpublished":"2023-01-17T17:41:06.018036Z","dateupdated":"2023-01-23T14:36:26.452412Z","revision":4,"vrda_d1_directreport":null,"vrda_d1_population":null,"vrda_d1_impact":null,"cam_widelyknown":null,"cam_exploitation":null,"cam_internetinfrastructure":null,"cam_population":null,"cam_impact":null,"cam_easeofexploitation":null,"cam_attackeraccessrequired":null,"cam_scorecurrent":null,"cam_scorecurrentwidelyknown":null,"cam_scorecurrentwidelyknownexploited":null,"ipprotocol":null,"cvss_accessvector":null,"cvss_accesscomplexity":null,"cvss_authentication":null,"cvss_confidentialityimpact":null,"cvss_integrityimpact":null,"cvss_availabilityimpact":null,"cvss_exploitablity":null,"cvss_remediationlevel":null,"cvss_reportconfidence":null,"cvss_collateraldamagepotential":null,"cvss_targetdistribution":null,"cvss_securityrequirementscr":null,"cvss_securityrequirementsir":null,"cvss_securityrequirementsar":null,"cvss_basescore":null,"cvss_basevector":null,"cvss_temporalscore":null,"cvss_environmentalscore":null,"cvss_environmentalvector":null,"metric":null,"vulnote":80}