# CVE-2018-14824: Information disclosure in Delta Industrial Automation PMSoft

> An out-of-bounds read in Delta PMSoft allows attackers to read confidential information by processing malicious project files.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N`)
- **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:** No
- **Published:** 27 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-x5wj-5p39-rp5w

## What is CVE-2018-14824?

CVE-2018-14824 is a medium-severity vulnerability in Delta Industrial Automation PMSoft, published on 27 Sep 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

Delta Electronics Delta Industrial Automation PMSoft v2.11 or prior has an out-of-bounds read vulnerability that can be executed when processing project files, which may allow an attacker to read confidential information.

Weakness: CWE-125 (Out-of-bounds Read)

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

It affects 1 product.


Products: Deltaww Delta Industrial Automation Pmsoft.

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

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

## Is CVE-2018-14824 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14824 is a medium-severity vulnerability in Delta Industrial Automation PMSoft, published on 27 Sep 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-14824 in the wild and no public exploit code.

Affected product: Delta Industrial Automation PMSoft. 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-14824/ (Markdown: https://insights.sbomify.com/CVE-2018-14824/index.md)
```

## Sources

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

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