# CVE-2018-10774: Denial of service in n/a

> Remote attackers can cause a denial of service via a read access violation in the bibutils library, affecting applications using this component.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-10774, GHSA-2jwc-cq89-gvr8, UBUNTU-CVE-2018-10774

## What is CVE-2018-10774?

CVE-2018-10774 is a medium-severity denial of service vulnerability in n/a, published on 7 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Read access violation in the isiin_keyword function in isiin.c in libbibutils.a in bibutils through 6.2 allows remote attackers to cause a denial of service (application crash), as demonstrated by isi2xml.

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

## Which versions are affected by CVE-2018-10774?

It affects 1 product.


Products: Bibutils Project Bibutils.

## How do I fix CVE-2018-10774?

Upgrade to a fixed version.

## Is CVE-2018-10774 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-10773](https://insights.sbomify.com/CVE-2018-10773/): Null dereference in n/a (medium 6.5)
- [CVE-2018-10775](https://insights.sbomify.com/CVE-2018-10775/): Null dereference in n/a (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-10774 and fix it if it is affected.

What it is: CVE-2018-10774 is a medium-severity denial of service vulnerability in n/a, published on 7 May 2018. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-10774 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-2018-10774/ (Markdown: https://insights.sbomify.com/CVE-2018-10774/index.md)
```

## Sources

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

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