LiveActive security incident?Get immediate response
CVE Record

CVE-2024-48784: An Incorrect Access Control issue in SAMPMAX com.sampmax.homemax 2.1.2.7 allows a remote attacker to obtain...

An Incorrect Access Control issue in SAMPMAX com.sampmax.homemax 2.1.2.7 allows a remote attacker to obtain sensitive information via the firmware update process.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2024-48784 is a critical access-control flaw tied to SAMPMAX com.sampmax.homemax 2.1.2.7. The public record says a remote unauthenticated attacker may obtain sensitive information through the firmware update process. The source bundle does not name a vendor patch or confirmed exploitation.

Executive priority

Treat this as urgent where the named package/version is present, especially if firmware update paths are internet-reachable. Prioritize inventory and containment first because patch and product-scope details are incomplete in the public record.

Technical view

The CVE is classified as CWE-863, Incorrect Authorization, with CVSS 3.1 score 9.8 and vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. The described weakness affects the firmware update process in com.sampmax.homemax 2.1.2.7, but structured affected-product and CPE data are incomplete.

Likely exposure

Exposure is most likely in environments using SAMPMAX com.sampmax.homemax version 2.1.2.7 or dependent firmware-update workflows. The bundle does not identify broader affected versions, CPEs, device models, or deployment patterns.

Exploitation context

The CVSS vector indicates remote, low-complexity, unauthenticated exploitation with no user interaction. However, the source bundle does not show CISA KEV listing, active exploitation, public exploit tooling, or operational attack reports.

Researcher notes

The strongest evidence is the CVE record, CVSS vector, CWE-863 classification, and linked researcher report. Key gaps are missing CPE data, unclear product ownership, no named fix, and no evidence of exploitation in KEV or the provided sources.

Mitigation direction

  • Check SAMPMAX or product-owner guidance for fixed versions or official mitigations.
  • Remove or disable affected com.sampmax.homemax 2.1.2.7 deployments where feasible.
  • Restrict access to firmware update workflows to trusted networks only.
  • Monitor update-related traffic for unexpected access or data exposure.
  • Review secrets or sensitive files that may be exposed by firmware update handling.

Validation and detection

  • Inventory systems or apps using com.sampmax.homemax 2.1.2.7.
  • Confirm whether firmware update functionality is reachable from untrusted networks.
  • Review vendor advisories and the linked researcher report for affected-version clarification.
  • Check logs for anomalous firmware update requests or unexpected downloads.
  • Document compensating controls if no vendor fix is available.
Prepared
Confidence
medium
Sources
3

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 · medium confidence lookup

CWE-863: Authorization and privilege behavior lookup

Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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
cve · low confidence lookup

CVE-2024-48784 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2024-48784Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

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

CWE-863 · source CWE mapping

Incorrect Authorization

Incorrect Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.