# CVE-2013-4758: Use after free in n/a

> Remote attackers can cause a crash or execute code via crafted JSON responses in rsyslog's Elasticsearch plugin when local error logging is enabled.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Oct 2013
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h9vm-3m8j-cpjv

## What is CVE-2013-4758?

CVE-2013-4758 is a medium-severity use after free vulnerability in n/a, published on 4 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Double free vulnerability in the writeDataError function in the ElasticSearch plugin (omelasticsearch) in rsyslog before 7.4.2 and before 7.5.2 devel, when errorfile is set to local logging, allows remote attackers to cause a denial of service (crash) and possibly execute arbitrary code via a crafted JSON response.

Weakness: CWE-399

## Which versions are affected by CVE-2013-4758?

It affects 1 product.


Products: Rsyslog Rsyslog.

## How do I fix CVE-2013-4758?

Upgrade to a fixed version.

## Is CVE-2013-4758 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-17040](https://insights.sbomify.com/CVE-2019-17040/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-12588](https://insights.sbomify.com/CVE-2017-12588/): Other in n/a (critical 9.8)
- [CVE-2008-5617](https://insights.sbomify.com/CVE-2008-5617/): Auth bypass in n/a (high 8.5)
- [CVE-2014-3634](https://insights.sbomify.com/CVE-2014-3634/): Memory corruption in n/a (high 7.5)
- [CVE-2015-3243](https://insights.sbomify.com/CVE-2015-3243/): Information disclosure in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-4758 and fix it if it is affected.

What it is: CVE-2013-4758 is a medium-severity use after free vulnerability in n/a, published on 4 Oct 2013. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2013-4758 in the wild and no public exploit code.

Affected product: n/a. 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-2013-4758/ (Markdown: https://insights.sbomify.com/CVE-2013-4758/index.md)
```

## Sources

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

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