LiveActive security incident?Get immediate response
CVE Record

CVE-2021-45419: Certain Starcharge products are affected by Improper Input Validation.

Certain Starcharge products are affected by Improper Input Validation. The affected products include: Nova 360 Cabinet <= 1.3.0.0.7b102 - Fixed: Beta1.3.0.1.0 and Titan 180 Premium <= 1.3.0.0.6 - Fixed: 1.3.0.0.9.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

This CVE affects certain Starcharge EV charging products because input was not properly validated. The public record names affected firmware ranges and fixed versions, but does not provide a severity score, business impact details, or confirmed exploitation evidence.

Executive priority

Treat this as a targeted asset-management and patching issue for affected EV charging infrastructure. Prioritize confirmation and firmware remediation where these products support operationally important charging services.

Technical view

CVE-2021-45419 is an improper input validation issue affecting Starcharge Nova 360 Cabinet firmware up to 1.3.0.0.7b102 and Titan 180 Premium firmware up to 1.3.0.0.6. Fixed versions are listed as Beta1.3.0.1.0 and 1.3.0.0.9 respectively. No CVSS, CWE, or detailed impact is provided in the source bundle.

Likely exposure

Exposure appears limited to organizations operating the named Starcharge Nova 360 Cabinet or Titan 180 Premium products on affected firmware. The sources do not establish whether exposure requires network access, physical access, or authenticated access.

Exploitation context

The CVE is not listed as KEV in the provided bundle. No cited source in the bundle confirms active exploitation, public weaponization, or exploitation prerequisites.

Researcher notes

The public data is thin: no CVSS vector, CWE mapping, vulnerability mechanism, access requirements, or impact statement is included in the source bundle. Avoid assuming exploitability beyond improper input validation until vendor or researcher details are reviewed.

Mitigation direction

  • Inventory Starcharge Nova 360 Cabinet and Titan 180 Premium deployments.
  • Upgrade Nova 360 Cabinet to Beta1.3.0.1.0 or later vendor-approved firmware.
  • Upgrade Titan 180 Premium to 1.3.0.0.9 or later vendor-approved firmware.
  • Check Starcharge or VinCSS guidance for deployment-specific remediation details.
  • Track compensating controls if immediate firmware upgrade is not possible.

Validation and detection

  • Confirm exact product model and firmware version on each deployed charger.
  • Compare versions against the affected ranges in the CVE record.
  • Verify upgraded devices report the fixed firmware versions or later.
  • Review asset records for untracked EV charging infrastructure.
  • Document any devices awaiting vendor guidance or maintenance windows.
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.

cve · low confidence lookup

CVE-2021-45419 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
3Timeline events
1ADP providers
3Source links

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

CVECVE Program Container
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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