# CVE-2017-14727: Null dereference in n/a

> An attacker can cause a crash in WeeChat by exploiting an uninitialized buffer in the logger plugin's date/time formatting.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** ALPINE-CVE-2017-14727, DEBIAN-CVE-2017-14727, DLA-1111-1, GHSA-ppv9-cgrm-wr3p, MGASA-2017-0369, UBUNTU-CVE-2017-14727

## What is CVE-2017-14727?

CVE-2017-14727 is a high-severity vulnerability in n/a, published on 23 Sep 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

logger.c in the logger plugin in WeeChat before 1.9.1 allows a crash via strftime date/time specifiers, because a buffer is not initialized.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-14727?

It affects 1 product.


Products: Weechat Logger.

## How do I fix CVE-2017-14727?

Upgrade to a fixed version.

## Is CVE-2017-14727 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-14727 and fix it if it is affected.

What it is: CVE-2017-14727 is a high-severity vulnerability in n/a, published on 23 Sep 2017. 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-2017-14727 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-2017-14727/ (Markdown: https://insights.sbomify.com/CVE-2017-14727/index.md)
```

## Sources

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

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