# CVE-2014-3683: Integer overflow in n/a

> Remote attackers can cause a denial of service crash in rsyslog by sending a large priority value due to an integer overflow.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/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:** 2 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3683, DSA-3047-1, GHSA-cj25-wc2v-fhxm, UBUNTU-CVE-2014-3683

## What is CVE-2014-3683?

CVE-2014-3683 is a medium-severity vulnerability in n/a, published on 2 Nov 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Integer overflow in rsyslog before 7.6.7 and 8.x before 8.4.2 and sysklogd 1.5 and earlier allows remote attackers to cause a denial of service (crash) via a large priority (PRI) value.  NOTE: this vulnerability exists because of an incomplete fix for CVE-2014-3634.

Weakness: CWE-189

## Which versions are affected by CVE-2014-3683?

It affects 2 products.


Products: Rsyslog Rsyslog, Sysklogd Project Sysklogd.

## How do I fix CVE-2014-3683?

Upgrade to a fixed version.

## Is CVE-2014-3683 being exploited?

There is no known exploitation of CVE-2014-3683 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-2013-4758](https://insights.sbomify.com/CVE-2013-4758/): Use after free in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3683 and fix it if it is affected.

What it is: CVE-2014-3683 is a medium-severity vulnerability in n/a, published on 2 Nov 2014. 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-2014-3683 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-2014-3683/ (Markdown: https://insights.sbomify.com/CVE-2014-3683/index.md)
```

## Sources

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

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