LiveActive security incident?Get immediate response
CVE Record

CVE-2024-48775: An issue in Plug n Play Camera com.ezset.delaney 1.2.0 allows a remote attacker to obtain sensitive informa...

An issue in Plug n Play Camera com.ezset.delaney 1.2.0 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-48775 describes a flaw in Plug n Play Camera package com.ezset.delaney version 1.2.0 where the firmware update process can expose sensitive information to a remote unauthenticated attacker.

Executive priority

Prioritize discovery first. The severity is high because no authentication is required and confidentiality impact is high, but urgency depends on whether this specific camera app or update workflow exists in the environment.

Technical view

The record maps to CWE-306 and CVSS 3.1 score 7.5: network reachable, low complexity, no privileges, no user interaction, high confidentiality impact, and no stated integrity or availability impact.

Likely exposure

Exposure appears limited to environments using Plug n Play Camera com.ezset.delaney 1.2.0 or related firmware update infrastructure. The CVE data does not identify a vendor, product CPE, device model, or broader affected versions.

Exploitation context

The sources do not show CISA KEV listing or active exploitation. Public evidence supports remote unauthenticated sensitive information exposure through the firmware update process, but does not establish real-world exploitation.

Researcher notes

The public record is sparse: affected vendor and product fields are n/a, and the only technical reference is a GitHub report. Do not generalize this CVE to unrelated camera brands without confirming shared code or update infrastructure.

Mitigation direction

  • Check vendor or maintainer guidance for an updated app or firmware process.
  • Inventory use of com.ezset.delaney version 1.2.0 in managed devices.
  • Limit affected camera systems and update endpoints to trusted networks.
  • Monitor for unexpected firmware update traffic or sensitive file retrievals.
  • Remove or replace unsupported deployments if no vendor fix exists.

Validation and detection

  • Confirm whether com.ezset.delaney 1.2.0 exists in mobile or device inventories.
  • Review camera firmware update paths for unauthenticated sensitive information exposure.
  • Check CVE and vendor sources for newer affected-version or patch details.
  • Correlate network logs for unusual access to firmware update resources.
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-48775 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-48775Attack 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.