CVE-2025-35983
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 Certificate Validation (CWE-295) in the Controller 7000 OneLink implementation could allow an unprivileged attacker to perform a limited denial of service or perform privileged overrides during the initial configuration of the Controller, there is no risk for Controllers once they are connected. This issue affects Controller 7000: 9.30 prior to vCR9.30.250624a (distributed in 9.30.1871 (MR1)).
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 certificate validation (CWE-295) in the Controller 7000 OneLink implementation allows an unprivileged attacker to perform limited DoS or privileged overrides during the initial configuration phase only. Once the Controller is connected and configured, the vulnerability does not pose a risk.
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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:L
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 the Controller 7000 deployment phaseDetermine whether the Controller 7000 is currently in its initial configuration phase (not yet connected to the network/OneLink) or has already completed setup and is operationalAffected if The device is in initial configuration phase (not yet connected) - if already connected and configured, this vulnerability does not apply
-
Determine the installed firmware versionAccess the Controller 7000 admin interface or check the system information via CLI command (typically 'show version' or 'system info') to retrieve the current firmware/software versionAffected if Version is earlier than vCR9.30.250624a (the fixed release)
-
Confirm OneLink feature is enabledVerify that the OneLink feature/implementation is active on the Controller 7000 - check configuration status via admin panel or CLI command such as 'show onelink status' or similar configuration display commandAffected if OneLink is enabled and the device is still in initial setup phase
You are affected only if the Controller 7000 is running a version earlier than vCR9.30.250624a AND is currently in the initial configuration phase (not yet connected to OneLink). Already-configured Controllers are not at risk.
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.
dbcve · scopedUpgrade Controller 7000 to vCR9.30.250624a or later to remediate the improper certificate validation. This is only applicable during initial setup/configuration; already-connected Controllers are not affected.
vCR9.30.250624a (distributed in 9.30.1871 MR1)
- Obtain the fixed firmware version vCR9.30.250624a (also distributed as 9.30.1871 MR1) from the official Gallagher download portal or support channels
- Access the Controller 7000 management interface
- Navigate to the firmware/software update section
- Upload and apply the vCR9.30.250624a firmware to the Controller 7000
- Allow the controller to complete the update process
- Verify the controller is running the fixed version (vCR9.30.250624a or 9.30.1871 MR1)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-35983 — 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-35983 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