# CVE-2019-5919: Nablarch Incomplete Cryptography

> Weak cryptography in Nablarch allows attackers to read or modify stored data via hidden tags.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Mar 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-hmx6-gc2p-5p82

## What is CVE-2019-5919?

CVE-2019-5919 is a critical vulnerability in TIS Inc. Nablarch 5, published on 12 Mar 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An incomplete cryptography of the data store function by using hidden tag in Nablarch 5 (5, and 5u1 to 5u13) allows remote attackers to obtain information of the stored data, to register invalid value, or alter the value via unspecified vectors.

Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2019-5919?

2 open source packages ship an affected version, including com.nablarch.framework:nablarch-fw-web. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `com.nablarch.framework:nablarch-fw-web` | Maven | All versions | 1.5.1 |
| `com.nablarch.framework:nablarch-fw-web` | Maven | All versions | 1.5.1 |

Products: Nablarch Project Nablarch.

## How do I fix CVE-2019-5919?

Upgrade com.nablarch.framework:nablarch-fw-web to 1.5.1 or later.

## Is CVE-2019-5919 being exploited?

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

## Other vulnerabilities in TIS Inc. Nablarch 5

- [CVE-2019-5918](https://insights.sbomify.com/CVE-2019-5918/): XML external entity in Nablarch 5 (critical 9.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-5919 and fix it if it is affected.

What it is: CVE-2019-5919 is a critical vulnerability in TIS Inc. Nablarch 5, published on 12 Mar 2019. 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-2019-5919 in the wild and no public exploit code.

Affected packages and fixed versions:
- com.nablarch.framework:nablarch-fw-web (Maven): affected all versions; fixed in 1.5.1
- com.nablarch.framework:nablarch-fw-web (Maven): affected all versions; fixed in 1.5.1

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-2019-5919/ (Markdown: https://insights.sbomify.com/CVE-2019-5919/index.md)
```

## Sources

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

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