dbcve.org
Kerio ControlApplication · Gfi

CVE-2025-34070

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 missing authentication vulnerability in the GFIAgent component of GFI Kerio Control 9.4.5 allows unauthenticated remote attackers to perform privileged operations. The GFIAgent service, responsible for integration with GFI AppManager, exposes HTTP services on ports 7995 and 7996 without proper authentication. The /proxy handler on port 7996 allows arbitrary forwarding to administrative endpoints when provided with an Appliance UUID, which itself can be retrieved from port 7995. This results in a complete authentication bypass, permitting access to sensitive administrative APIs.

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

Missing authentication in GFI Kerio Control's GFIAgent component allows unauthenticated attackers to access administrative APIs. The service on ports 7995 and 7996 exposes endpoints without authentication; attackers can retrieve an Appliance UUID from port 7995 and use it on port 7996's /proxy handler to forward requests to privileged administrative endpoints, achieving complete authentication bypass.

MitigationRestrict network access to ports 7995 and 7996 via firewall rules until a vendor patch is available; monitor for unauthorized access attempts to these ports.

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. Check if GFI Kerio Control is running and listening on ports 7995 or 7996
    Run 'netstat -an | grep -E "(7995|7996)"' or 'ss -tlnp | grep -E "(7995|7996)"' to see if these ports are open and listening
    Affected if Ports 7995 or 7996 are listening and accepting connections indicates the vulnerable service is exposed
  2. Identify the installed GFI Kerio Control version
    Check the installed version via the web admin interface, or run 'kerio-control version' if CLI access is available, or inspect installed packages
    Affected if Version is exactly 9.4.5 which is the affected version listed
  3. Verify if the GFIAgent component is enabled
    Check the product configuration for GFIAgent service status, or inspect running processes for 'GFIAgent' or 'gfiagent' processes
    Affected if GFIAgent is running as a service and accepting connections on ports 7995/7996
  4. Test unauthenticated access to port 7995 endpoint
    Send an HTTP GET request to http://<target>:7995/ without any authentication headers and check for a response containing an Appliance UUID
    Affected if The endpoint returns an Appliance UUID without requiring authentication indicates the vulnerability is present
  5. Test proxy forwarding on port 7996
    Send an HTTP POST request to http://<target>:7996/proxy with the retrieved UUID and an embedded administrative API request to verify if privileged endpoints are accessible
    Affected if Administrative API calls can be forwarded through the proxy without authentication, confirming the authentication bypass

The environment is affected if GFI Kerio Control version 9.4.5 is running with the GFIAgent component exposed on network-accessible ports 7995 and/or 7996, allowing unauthenticated access to administrative APIs.

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 network access to ports 7995 and 7996 via firewall rules until a vendor patch is available; monitor for unauthorized access attempts to these ports.

Fix this in Kerio Control Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,690
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-34070 — 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-34070 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