# CVE-2018-12356: Code injection in n/a

> Attackers can spoof signatures to inject keys or modify scripts, leading to password disclosure or arbitrary code execution in Simple Password Store.

- **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:** Yes
- **Published:** 15 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** DEBIAN-CVE-2018-12356, GHSA-j8m7-7fm4-j768, UBUNTU-CVE-2018-12356, openSUSE-SU-2024:11150-1

## What is CVE-2018-12356?

CVE-2018-12356 is a critical code injection vulnerability in n/a, published on 15 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in password-store.sh in pass in Simple Password Store 1.7.x before 1.7.2. The signature verification routine parses the output of GnuPG with an incomplete regular expression, which allows remote attackers to spoof file signatures on configuration files and extension scripts. Modifying the configuration file allows the attacker to inject additional encryption keys under their control, thereby disclosing passwords to the attacker. Modifying the extension scripts allows the attacker arbitrary code execution.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature)

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

It affects 1 product.


Products: Simple Password Store Project Simple Password Store.

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

Upgrade to a fixed version.

## Is CVE-2018-12356 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-12356 is a critical code injection vulnerability in n/a, published on 15 Jun 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-12356 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-12356/ (Markdown: https://insights.sbomify.com/CVE-2018-12356/index.md)
```

## Sources

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

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