LiveActive security incident?Get immediate response
CVE Record

CVE-2019-25062: Sricam IP CCTV Camera Device Viewer stack-based overflow

A vulnerability was found in Sricam IP CCTV Camera and classified as critical. This issue affects some unknown processing of the component Device Viewer. The manipulation leads to memory corruption. An attack has to be approached locally. The exploit has been disclosed to the public and may be used.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2019-25062 is a memory corruption flaw in the Device Viewer component of Sricam IP CCTV Camera. The available sources describe local, low-privilege exploitation with limited confidentiality, integrity, and availability impact. A public exploit reference exists, but the bundle does not show KEV-listed or confirmed active exploitation.

Executive priority

Treat this as a moderate operational risk for CCTV environments, especially where camera management systems are shared or weakly controlled. Prioritize inventory, access restriction, and vendor guidance review before broader remediation planning.

Technical view

The issue is classified as CWE-121 stack-based overflow. The CVSS 3.1 vector is AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L, score 5.3. Affected versions are listed as unknown or n/a, and no CPEs are provided. Sources do not name a vendor patch or mitigation.

Likely exposure

Exposure is most likely in environments using Sricam IP CCTV Camera devices with the affected Device Viewer component. The version scope is unclear, so asset owners should not assume a device is safe based only on model name. Local access and low privileges are required according to the CVSS vector.

Exploitation context

The exploit has been publicly disclosed through a cited Exploit-DB reference. The source bundle does not indicate CISA KEV inclusion or verified active exploitation. The attack path is local, low complexity, requires low privileges, and does not require user interaction.

Researcher notes

Evidence is incomplete on affected versions, fixed releases, and exact vulnerable processing path. Do not generalize beyond Sricam IP CCTV Camera Device Viewer without confirming against source references. Public exploit disclosure raises validation priority, but the local attack requirement limits broad internet-scale exposure.

Mitigation direction

  • Inventory Sricam IP CCTV Camera deployments and firmware versions.
  • Check Sricam or device supplier guidance for fixed firmware or replacement advice.
  • Restrict local access to camera management systems and Device Viewer hosts.
  • Segment CCTV networks away from corporate user and server networks.
  • Remove unnecessary local user accounts and shared credentials.

Validation and detection

  • Confirm whether Device Viewer is installed or used with deployed Sricam cameras.
  • Record exact camera model, firmware, and viewer software versions.
  • Compare assets against CVE, VulDB, and Exploit-DB references.
  • Review local account access to systems managing CCTV devices.
  • Check security monitoring for unusual local access to CCTV management hosts.
Prepared
Confidence
medium
Sources
4

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-121: 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-2019-25062 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
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

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

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

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
5.3CVSS 3.1MediumCVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L1.83.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2019-25062Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
SricamIP CCTV Cameran/aListed
Weakness

CWE details

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

CWE-121 · source CWE mapping

Stack-based Buffer Overflow

Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.