LiveActive security incident?Get immediate response
CVE Record

CVE-2024-48788: An issue in YESCAM (com.yescom.YesCam.zwave) 1.0.2 allows a remote attacker to obtain sensitive information...

An issue in YESCAM (com.yescom.YesCam.zwave) 1.0.2 allows a remote attacker to obtain sensitive 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-48788 reports that YESCAM package com.yescom.YesCam.zwave version 1.0.2 can expose sensitive information through its firmware update process. The main business risk is confidentiality loss, not system takeover or outage, based on the published CVSS vector.

Executive priority

Treat as high priority where the named package is deployed, especially in environments handling sensitive device, account, or network information. Priority is lower where asset inventory confirms the package is absent.

Technical view

The CVE is mapped to CWE-319 and scored CVSS 3.1 7.5: network exploitable, low complexity, no privileges, no user interaction, high confidentiality impact, no integrity or availability impact. The source bundle does not name a patched version or vendor mitigation.

Likely exposure

Exposure appears limited to environments using YESCAM com.yescom.YesCam.zwave 1.0.2. The CVE record does not provide normalized vendor, product, CPE, or version-range metadata, so asset matching may require application/package inventory review.

Exploitation context

The CVE is not listed as KEV in the supplied bundle, and no cited source states active exploitation. The published vector indicates remote unauthenticated information disclosure through the firmware update process, but source detail is limited.

Researcher notes

The public metadata is sparse: affected vendor/product fields are n/a, and the only technical reference is the external report. Avoid broad product assumptions until the referenced package and version are confirmed in the environment.

Mitigation direction

  • Check vendor or maintainer guidance for patched versions or configuration changes.
  • Inventory YESCAM com.yescom.YesCam.zwave installations and identify version 1.0.2.
  • Limit firmware update activity to trusted networks where operationally feasible.
  • Monitor the CVE record and referenced report for remediation updates.

Validation and detection

  • Confirm whether com.yescom.YesCam.zwave 1.0.2 exists in managed assets.
  • Review firmware update traffic handling using approved internal testing procedures.
  • Check whether sensitive data is transmitted without appropriate protection.
  • Document compensating controls around update paths and network access.
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 · low confidence lookup

CWE-319: 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
cve · low confidence lookup

CVE-2024-48788 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-48788Attack 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-319 · source CWE mapping

Cleartext Transmission of Sensitive Information

Cleartext Transmission of Sensitive Information represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.