# CVE-2024-11949: GFI Archiver Store Service Deserialization of Untrusted Data Remote Code Execution Vulnerability

> Remote attackers with authentication can execute arbitrary code as SYSTEM via deserialization in GFI Archiver Store Service.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Dec 2024
- **Updated:** 12 Dec 2024
- **Also known as:** GHSA-p2gm-hcx7-mr3w

## What is CVE-2024-11949?

CVE-2024-11949 is a high-severity unsafe deserialization vulnerability in GFI Archiver, published on 11 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2024-11949?

It affects 1 product.


Products: Gfi Archiver.

## How do I fix CVE-2024-11949?

No fix has been published for CVE-2024-11949 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-11949 being exploited?

There is no known exploitation of CVE-2024-11949 in the wild and no public exploit code.

## Other vulnerabilities in GFI Archiver

- [CVE-2024-11948](https://insights.sbomify.com/CVE-2024-11948/): GFI Archiver Telerik Web UI Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2021-29281](https://insights.sbomify.com/CVE-2021-29281/): File upload in n/a (critical 9.8)
- [CVE-2026-2036](https://insights.sbomify.com/CVE-2026-2036/): GFI Archiver MArc.Store Deserialization of Untrusted Data Remote Code Execution Vulnerability (high 8.8)
- [CVE-2026-2037](https://insights.sbomify.com/CVE-2026-2037/): GFI Archiver MArc.Core Deserialization of Untrusted Data Remote Code Execution Vulnerability (high 8.8)
- [CVE-2024-11947](https://insights.sbomify.com/CVE-2024-11947/): GFI Archiver Core Service Deserialization of Untrusted Data Remote Code Execution Vulnerability (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11949 and fix it if it is affected.

What it is: CVE-2024-11949 is a high-severity unsafe deserialization vulnerability in GFI Archiver, published on 11 Dec 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-11949 in the wild and no public exploit code.

Affected product: GFI Archiver. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-11949/ (Markdown: https://insights.sbomify.com/CVE-2024-11949/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11949
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11949
- OSV: https://osv.dev/vulnerability/CVE-2024-11949

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-11949/
Summaries are generated and may contain mistakes; the official description above is the record.