CVE-2021-25910
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 · uneditedImproper Authentication vulnerability in the cookie parameter of ZIV AUTOMATION 4CCT-EA6-334126BF allows a local attacker to perform modifications in several parameters of the affected device as an authenticated user.
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 confidenceImproper authentication in the cookie parameter of ZIV Automation 4CCT-EA6-334126BF allows a local authenticated attacker to manipulate device parameters by modifying the cookie value. The vulnerability permits unauthorized modifications to several device settings despite the attacker having only basic authenticated access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 3.23.77.8.33251CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Identify device modelLocate the device label or system information page showing the model number. Look for '4CCT-EA6-334126BF' or 'Zivautomation' branding on the physical device or in the device's web interface/system settings.Affected if The device is a ZIV Automation 4CCT-EA6-334126BF unit
-
Check firmware versionAccess the device's administrative interface (web UI, serial console, or management console) and navigate to the firmware version or system information section. Compare the displayed firmware version against 3.23.77.8.33251.Affected if Firmware version equals exactly 3.23.77.8.33251
-
Verify web interface is enabledCheck if the device's web-based management interface is accessible and active. This is typically on ports 80 or 443, or a custom HTTP port defined in the device configuration.Affected if Web interface is enabled and accessible with authentication
-
Confirm cookie-based session managementInspect the authentication mechanism used by the web interface. Log in and examine how session state is maintained - check for cookie-based authentication tokens in browser developer tools or by reviewing HTTP response headers.Affected if Session authentication relies on cookie values that can be modified
-
Test parameter modification accessWith standard authenticated access, attempt to modify device parameters (network settings, device configuration, or system options) through the web interface. Observe if changes are accepted without additional authorization prompts beyond the initial login cookie.Affected if Parameter modifications succeed with only basic authenticated access using a modifiable cookie value
A user is affected if they have a ZIV Automation 4CCT-EA6-334126BF device running firmware version 3.23.77.8.33251 with the web interface enabled and cookie-based authentication in use.
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 dataImplement proper server-side validation of cookie values and enforce strict authorization checks on all parameter modification operations. Contact vendor for firmware patch addressing cookie authentication bypass.
- Consultation8.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,776.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-25910 — 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-2021-25910 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