CVE-2025-52268
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedStarCharge Artemis AC Charger 7-22 kW v1.0.4 was discovered to contain a hardcoded AES key which allows attackers to forge or decrypt valid login tokens.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe StarCharge Artemis AC Charger v1.0.4 contains a hardcoded AES encryption key embedded in the firmware. Since this symmetric key is static and discoverable (likely through firmware extraction or reverse engineering), attackers can decrypt existing login tokens or craft forged tokens to authenticate as any user, achieving full authentication bypass.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm device model and firmware versionAccess the device admin interface or check the firmware version via the device's web console, API endpoint, or physical display. Look for 'StarCharge Artemis AC Charger' and version '1.0.4'.Affected if The device is a StarCharge Artemis AC Charger running firmware version 1.0.4.
-
Determine if remote management is enabledCheck the device network settings or admin interface for remote access or cloud connectivity features. Look for options like 'Enable Remote Management', 'Cloud API Access', or 'Network API' that allow external authentication.Affected if Remote management or API access is enabled, allowing external token-based authentication.
-
Check if token-based authentication is in useInspect the authentication mechanism used by the device web interface or API. Look for session tokens, JWT tokens, or bearer tokens in login responses or API calls.Affected if The device uses token-based authentication for user login or API access.
-
Inspect firmware for hardcoded AES keyExtract the firmware image (via firmware update file, JTAG, or debug interface) and analyze binary or strings for AES-related constants or the key itself. Look for 16-byte or 32-byte hex patterns that may represent AES-128 or AES-256 keys.Affected if A static, hardcoded AES key is found embedded in the firmware binary.
You are affected if you have a StarCharge Artemis AC Charger on firmware version 1.0.4 with remote access or token-based authentication enabled, as the hardcoded AES key could allow attackers to forge or decrypt authentication tokens.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace the hardcoded AES key with dynamically generated keys stored securely (e.g., hardware security module or secure enclave), implement proper key management with rotation, invalidate all existing tokens, and push a firmware update to patch the exposed key.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52268 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52268 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data