# CVE-2023-49275: Wazuh vulnerable to NULL Pointer Dereference in wazuh-analysisd

> A malicious client can cause a denial of service in the Wazuh analysis engine by sending a malformed syscollector message lacking a timestamp.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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:** 19 Apr 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-4mq7-w9r6-9975

## What is CVE-2023-49275?

CVE-2023-49275 is a medium-severity vulnerability in Wazuh Wazuh, published on 19 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Wazuh is a free and open source platform used for threat prevention, detection, and response. A NULL pointer dereference was detected during fuzzing of the analysis engine, allowing malicious clients to DoS the analysis engine. The bug occurs when `analysisd` receives a syscollector message with the `hotfix` `msg_type` but lacking a `timestamp`. It uses `cJSON_GetObjectItem()` to get the `timestamp` object item and dereferences it without checking for a `NULL` value. A malicious client can DoS the analysis engine. This vulnerability is fixed in 4.7.1.

Weakness: CWE-476 (NULL Pointer Dereference)

## Which versions are affected by CVE-2023-49275?

It affects 1 product.


Products: Wazuh Wazuh.

## How do I fix CVE-2023-49275?

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

## Is CVE-2023-49275 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49275 exists.

## Other vulnerabilities in Wazuh Wazuh

- [CVE-2025-24016](https://insights.sbomify.com/CVE-2025-24016/): Wazuh Server Deserialization of Untrusted Data (critical 9.9, exploited in the wild)
- [CVE-2024-32038](https://insights.sbomify.com/CVE-2024-32038/): Wazuh Analysis Engine Event Decoder Heap-based Buffer Overflow Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2021-44079](https://insights.sbomify.com/CVE-2021-44079/): Command injection in n/a (critical 9.8)
- [CVE-2024-1243](https://insights.sbomify.com/CVE-2024-1243/): Remote code execution and local privilege escalation in Wazuh Windows agent via NetNTLMv2 hash theft (critical 9.5)
- [CVE-2026-61800](https://insights.sbomify.com/CVE-2026-61800/): Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893) (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-49275 and fix it if it is affected.

What it is: CVE-2023-49275 is a medium-severity vulnerability in Wazuh Wazuh, published on 19 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-49275 exists.

Affected product: Wazuh Wazuh. 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-2023-49275/ (Markdown: https://insights.sbomify.com/CVE-2023-49275/index.md)
```

## Sources

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

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