LiveActive security incident?Get immediate response
CVE Record

CVE-2022-4499: The strcmp function in TP-Link routers, Archer C5 and WR710N-V1, used for checking credentials in httpd, is susceptible to a side-channel attack.

TP-Link routers, Archer C5 and WR710N-V1, using the latest software, the strcmp function used for checking credentials in httpd, is susceptible to a side-channel attack. By measuring the response time of the httpd process, an attacker could guess each byte of the username and password.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Some TP-Link Archer C5 and WR710N routers may leak login information through tiny response-time differences. An unauthenticated network attacker could potentially infer the username and password byte by byte. The sources do not identify active exploitation or a fixed firmware version.

Executive priority

Treat as a high-priority network edge risk where affected routers are present. Prioritize identifying exposed management interfaces and deciding whether update, isolation, or replacement is required.

Technical view

CVE-2022-4499 is a timing side-channel in httpd credential checking caused by use of strcmp. A remote unauthenticated attacker could measure response timing to infer credentials. CVSS is 7.5 high, with network access, low complexity, no privileges, no user interaction, and high confidentiality impact.

Likely exposure

Exposure is limited to TP-Link WR710N V1-151022 and Archer C5 V2_160221_US devices running the affected software, especially where the router management service is reachable from untrusted networks.

Exploitation context

The bundle states credential inference is possible by response-time measurement. KEV is false, and the provided sources do not claim active exploitation, public weaponization, or observed attacks.

Researcher notes

Evidence supports a timing side-channel in credential comparison, not authentication bypass by itself. The source bundle does not provide patch details, affected CPEs, exploit telemetry, or proof of active exploitation.

Mitigation direction

  • Check TP-Link and CERT VU#572615 for current remediation or replacement guidance.
  • Restrict router management access to trusted administrative networks only.
  • Remove affected management interfaces from internet exposure where possible.
  • Replace affected devices if no supported fixed firmware is available.
  • Rotate router credentials after remediation if exposure is suspected.

Validation and detection

  • Inventory TP-Link Archer C5 and WR710N devices in use.
  • Compare firmware versions against Archer C5 V2_160221_US and WR710N V1-151022.
  • Confirm router management httpd is not reachable from untrusted networks.
  • Review CERT VU#572615 and TP-Link guidance for updated status.
  • Document whether compensating network restrictions are in place.
Prepared
Confidence
high
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-676: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-4499 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
7.5 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
7.5CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N3.93.6Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2022-4499Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TP-LinkWR710NV1-151022Listed
TP-LinkArcher C5V2_160221_USListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-676 · source CWE mapping

Use of Potentially Dangerous Function

Use of Potentially Dangerous Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.