# CVE-2018-14043: Missing authorization in n/a

> An attacker can read sensitive data by exploiting incorrect file access controls during copy operations in the mstdlib C library.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jul 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-h432-5g5p-5gfj

## What is CVE-2018-14043?

CVE-2018-14043 is a critical missing authorization vulnerability in n/a, published on 13 Jul 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mstdlib (aka the M Standard Library for C) 1.2.0 has incorrect file access control in situations where M_fs_perms_can_access attempts to delete an existing file (that lacks public read/write access) during a copy operation, related to fs/m_fs.c and fs/m_fs_path.c. An attacker could create the file and then would have access to the data.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Monetra Mstdlib.

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

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

## Is CVE-2018-14043 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-14043 is a critical missing authorization vulnerability in n/a, published on 13 Jul 2018. 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-2018-14043 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-14043/ (Markdown: https://insights.sbomify.com/CVE-2018-14043/index.md)
```

## Sources

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

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