CVE-2025-34069
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 · uneditedAn authentication bypass vulnerability exists in GFI Kerio Control 9.4.5 due to insecure default proxy configuration and weak access control in the GFIAgent service. The non-transparent proxy on TCP port 3128 can be used to forward unauthenticated requests to internal services such as GFIAgent, bypassing firewall restrictions and exposing internal management endpoints. This enables unauthenticated attackers to access the GFIAgent service on ports 7995 and 7996, retrieve the appliance UUID, and issue administrative requests via the proxy. Exploitation results in full administrative access to the Kerio Control appliance.
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 confidenceGFI Kerio Control 9.4.5 contains an authentication bypass via its non-transparent proxy on TCP port 3128. The proxy improperly forwards unauthenticated requests to internal GFIAgent services listening on ports 7995 and 7996, bypassing firewall restrictions. Attackers can retrieve the appliance UUID and issue administrative requests through this proxy chain, achieving full administrative access to the appliance.
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= 9.4.5CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed GFI Kerio Control versionUse system inventory or version check command for GFI Kerio Control (e.g., via admin UI, CLI show version, or package manager)Affected if Version is exactly 9.4.5
-
Verify proxy service status on TCP port 3128Check if the non-transparent proxy service is enabled and listening on port 3128 (e.g., via netstat, ss, or admin UI proxy settings)Affected if Proxy is enabled and bound to TCP port 3128
-
Confirm internal GFIAgent ports are reachable through proxyTest if unauthenticated requests to the proxy on 3128 can be forwarded to internal services on ports 7995 and 7996 (e.g., curl via proxy to localhost:7995)Affected if Proxy permits forwarding to internal ports 7995/7996 without authentication
-
Check firewall rules for internal management portsInspect firewall configuration to determine if external access to ports 7995 and 7996 is blocked or if the proxy bypasses these restrictionsAffected if Firewall allows proxy-mediated access to internal GFIAgent services from untrusted networks
A system is affected if it runs GFI Kerio Control version 9.4.5 with the non-transparent proxy enabled on port 3128, and that proxy can forward unauthenticated requests to internal GFIAgent services on ports 7995/7996.
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 dataRestrict or disable unauthenticated access to the proxy on port 3128, implement proper access controls on GFIAgent ports 7995/7996, and apply vendor patches when available.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-34069 — 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-34069 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