dbcve.org
ArchiverApplication · Gfi

CVE-2024-11949

HIGH · 8.8 CVSS v3.1 Published 2024-12-12
Fix available
A fix is available. Upgrade to 15.7 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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
GFI Archiver Store Service Deserialization of Untrusted Data Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of GFI Archiver. Authentication is required to exploit this vulnerability. The specific flaw exists within the Store Service, which listens on TCP port 8018 by default. The issue results from the lack of proper validation of user-supplied data, which can result in deserialization of untrusted data. An attacker can leverage this vulnerability to execute code in the context of SYSTEM. Was ZDI-CAN-24331.

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 Archiver Store Service on TCP port 8018 lacks proper validation of user-supplied data, enabling deserialization of untrusted data. An authenticated attacker can exploit this to execute arbitrary code in the context of SYSTEM, achieving full remote code execution on affected installations.

MitigationRestrict network access to port 8018 to minimize attack surface; apply vendor security patches when available; if the Store Service is not required in the environment, consider disabling it.

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
ArchiverApplication
Affected:< 15.7

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 Archiver is installed
    Check for GFI Archiver installation: look for the application in Windows Programs and Features, or check for the installation directory (commonly in C:\Program Files\GFI\Archiver or similar). Note the installed version number.
    Affected if GFI Archiver is installed and the version is below 15.7 (e.g., 15.6, 15.5, earlier versions).
  2. Confirm Store Service is running on port 8018
    Open a command prompt and run: netstat -ano | findstr 8018. This will show if TCP port 8018 is in LISTENING state. Alternatively, check Windows Services for 'GFI Archiver Store Service' and verify its status is Running.
    Affected if The Store Service is listening on port 8018 (indicates the vulnerable component is active).
  3. Check network binding exposure
    Run: netsh interface ipv4 show boundtcp. Or check the GFI Archiver configuration to see which IP addresses the Store Service is bound to. Also verify firewall rules allow inbound connections to port 8018.
    Affected if Port 8018 is bound to 0.0.0.0 or is accessible from network hosts beyond localhost, increasing exposure to remote attack.
  4. Verify authentication is not hardened
    Review GFI Archiver authentication settings: check if default credentials are in use, if weak authentication is enabled, or if anonymous access is permitted to the Store Service API.
    Affected if The service allows authenticated attacker access (any valid user credentials can be used to exploit the deserialization flaw).

A user is affected if GFI Archiver version is below 15.7 AND the Store Service is running and exposed on TCP port 8018, enabling a remote authenticated attacker to deserialize untrusted data and execute code as SYSTEM.

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.

dbcve · scoped
Upgrade available Upgrade to 15.7 or later
Fixed in 15.7
Interim mitigation

Restrict network access to port 8018 to minimize attack surface; apply vendor security patches when available; if the Store Service is not required in the environment, consider disabling it.

Recommended fix Moderate confidence

GFI Archiver version 15.7

  1. Identify the current GFI Archiver version by checking the application's About or version information
  2. Download GFI Archiver version 15.7 or later from the official GFI website or vendor portal
  3. Review release notes to confirm the fix addresses CVE-2024-11949
  4. Schedule a maintenance window and backup the current configuration
  5. Stop the GFI Archiver services before upgrading
  6. Install version 15.7 following the vendor's standard upgrade procedure
  7. Restart the GFI Archiver services after installation
  8. Verify the Store Service is running correctly on TCP port 8018
Caveat Review GFI Archiver 15.7 release notes for any configuration or feature changes that may affect your deployment; standard upgrade precautions apply

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Archiver Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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