LiveActive security incident?Get immediate response
CVE Record

CVE-2024-48774: An issue in Fermax Asia Pacific Pte Ltd com.fermax.vida 2.4.6 allows a remote attacker to obtain sensitve i...

An issue in Fermax Asia Pacific Pte Ltd com.fermax.vida 2.4.6 allows a remote attacker to obtain sensitve information via the firmware update process.

HighCVSS 7.5Not KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2024-48774 describes sensitive information exposure in Fermax Asia Pacific com.fermax.vida 2.4.6 during the firmware update process. The public record rates it high because a remote unauthenticated attacker may access confidential data without user interaction.

Executive priority

Prioritize discovery and vendor follow-up. This is a high-confidentiality issue with incomplete remediation detail, so urgency depends on whether the affected app or update workflow is present in your environment.

Technical view

The CVE lists CWE-306 and CVSS 3.1 score 7.5, vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. Public data identifies com.fermax.vida 2.4.6 and a firmware update process issue, but does not clarify exact exposed data, device models, or fixed versions.

Likely exposure

Organizations using Fermax VIDA/com.fermax.vida version 2.4.6 may be exposed. The source bundle does not provide CPEs, device model coverage, server-side components, or affected firmware versions beyond that application identifier.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no provided source claims active exploitation. The risk is still material because the CVSS vector indicates remote, low-complexity, unauthenticated access with high confidentiality impact.

Researcher notes

Public evidence is thin. The CVE record and linked report support an unauthenticated firmware-update information disclosure in com.fermax.vida 2.4.6, but do not provide enough detail to confirm exploit maturity, exact data exposed, or official remediation.

Mitigation direction

  • Identify any Fermax VIDA/com.fermax.vida 2.4.6 usage in your environment.
  • Check Fermax or maintainer guidance for a fixed version or supported workaround.
  • Limit firmware update access to trusted networks where operationally feasible.
  • Monitor firmware update services and logs for unusual remote access.
  • Avoid exposing update-related services directly to untrusted networks.

Validation and detection

  • Confirm installed application versions and related firmware update workflows.
  • Review vendor advisories for affected versions, patches, or configuration guidance.
  • Check whether update endpoints are reachable from untrusted networks.
  • Review logs for unexpected access to update resources.
  • Document whether sensitive data is exposed during approved update testing.
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-306: Credential and account abuse lookup

Authentication and credential weaknesses can make valid-account abuse and credential telemetry useful review starting points. 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-48774 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
3Timeline events
1ADP providers
2Source links

SSVC decision data

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

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.6CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

7.5High
CVSS 3.1 vector shape for CVE-2024-48774Attack 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

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-306 · source CWE mapping

Missing Authentication for Critical Function

Missing Authentication for Critical Function represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.