# CVE-2014-125066: emmflo yuko-bot denial of service

> Remote attackers can cause a denial of service in emmflo yuko-bot by manipulating the title argument.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **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:** 8 Jan 2023
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cvvh-7xcr-36pm

## What is CVE-2014-125066?

CVE-2014-125066 is a medium-severity denial of service vulnerability in emmflo yuko-bot, published on 8 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in emmflo yuko-bot. It has been declared as problematic. This vulnerability affects unknown code. The manipulation of the argument title leads to denial of service. The attack can be initiated remotely. The name of the patch is e580584b877934a4298d4dd0c497c79e579380d0. It is recommended to apply a patch to fix this issue. The identifier of this vulnerability is VDB-217636.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


Products: Yuko-Bot Project Yuko-Bot.

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

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

## Is CVE-2014-125066 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2014-125066 is a medium-severity denial of service vulnerability in emmflo yuko-bot, published on 8 Jan 2023. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-125066 in the wild and no public exploit code.

Affected product: emmflo yuko-bot. 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-125066/ (Markdown: https://insights.sbomify.com/CVE-2014-125066/index.md)
```

## Sources

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

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