dbcve.org
Kerio ControlApplication · Gfi

CVE-2025-34071

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A remote code execution vulnerability in GFI Kerio Control 9.4.5 allows attackers with administrative access to upload and execute arbitrary code through the firmware upgrade feature. The system upgrade mechanism accepts unsigned .img files, which can be modified to include malicious scripts within the upgrade.sh or disk image components. These modified upgrade images are not validated for authenticity or integrity, and are executed by the system post-upload, enabling root access.

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 confidence

GFI Kerio Control 9.4.5 contains a remote code execution vulnerability in its firmware upgrade mechanism. Attackers with administrative privileges can upload modified .img upgrade files containing malicious scripts within upgrade.sh or disk image components. The system fails to validate the authenticity or integrity of these upgrade images through signature verification, allowing arbitrary code execution with root privileges after upload.

MitigationRestrict administrative access to trusted personnel only. Implement cryptographic signature validation for all firmware images before execution. Until vendor patch is available, monitor administrative activities and consider disabling the upgrade feature if not required.

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
Kerio ControlApplication
Affected:= 9.4.5

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
High
Availability
High

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

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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify GFI Kerio Control version
    Access the administrative web interface or run 'kerio-control --version' via CLI to confirm the exact installed version matches 9.4.5
    Affected if The installed version is exactly 9.4.5
  2. Confirm firmware upgrade feature is accessible
    Log into the admin panel and navigate to the System or Upgrade section to determine if the firmware upload mechanism is available and not explicitly disabled
    Affected if The firmware upgrade/upload interface is accessible to administrative users
  3. Identify administrative accounts with upgrade permissions
    Review the list of users with administrative privileges, particularly those who can access the firmware upgrade functionality
    Affected if Multiple or untrusted accounts have administrative access to the upgrade mechanism
  4. Audit recent upgrade file uploads
    Check the system for any recently uploaded .img upgrade files in /var or temporary directories, and review logs for upgrade upload events
    Affected if Unexpected or unauthorized .img upgrade files exist on the system
  5. Detect root-level process anomalies
    Use 'ps aux' or process monitoring to identify any unexpected processes running with root privileges, especially if launched from non-standard upgrade paths
    Affected if Unknown processes are running with root privileges indicating potential post-exploitation

You are affected if you are running GFI Kerio Control version 9.4.5 and the firmware upgrade feature is accessible to your administrative users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict administrative access to trusted personnel only. Implement cryptographic signature validation for all firmware images before execution. Until vendor patch is available, monitor administrative activities and consider disabling the upgrade feature if not required.

Fix this in Kerio Control Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34071 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-34071 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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