CVE Intelligence
Skip to main content
MEDIUM

CVE-2024-52321

CVE-2024-52321 Vulnerability Analysis & Exploit Intelligence

Multiple SHARP routers contain an improper authentication vulnerability in the configuration backup function. The product's backup files containing sensitive information may be retrieved by a remote unauthenticated attacker.

Published Updated Sources: cvelistV5, jpcert

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

sharp

6 products listed

CVSS base

5.9

MEDIUM

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Partial

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

sharp

Products (6)

home 5g hr02wi fi station sh 52bwi fi station sh 54cwi fi station sh 05lpocketwifi 809shspeed wi fi next w07

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
5.9CVSS 3.0MEDIUM——cvelistV5

Weakness & attack patterns

  • CWE-497

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1614System Language Discovery

References

2 on the record

Elsewhere on this site

  • sharpevery CVE for this vendor
  • CWE-497other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.