# CVE-2018-1346: NetIQ eDirectory Denial of Service


- **Severity:** Low 3.1 (`CVSS:3.0/AV:A/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 21 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vf9x-hpmv-92qm

## What is CVE-2018-1346?

CVE-2018-1346 is a low-severity vulnerability in NetIQ eDirectory, published on 21 Mar 2018. 

### Official description

Addresses denial of service attack to eDirectory versions prior to 9.1.

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

It affects 1 product.


Products: Netiq Edirectory.

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

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

## Is CVE-2018-1346 being exploited?

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

## Other vulnerabilities in NetIQ eDirectory

- [CVE-2017-5186](https://insights.sbomify.com/CVE-2017-5186/): Weak cryptography in NetIQ/Novell iManager and eDirectory (high 7.5)
- [CVE-2018-12461](https://insights.sbomify.com/CVE-2018-12461/): Certificate Revocation Check failure (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-1346 is a low-severity vulnerability in NetIQ eDirectory, published on 21 Mar 2018. 
Exploitation: There is no known exploitation of CVE-2018-1346 in the wild and no public exploit code.

Affected product: NetIQ eDirectory. 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-1346/ (Markdown: https://insights.sbomify.com/CVE-2018-1346/index.md)
```

## Sources

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

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