Sign in Sign up
JA · EN · FR
SecPulse
This advisory has been withdrawn (2020-06-26).
Categories
CVE-2019-16303

Vulnerability in generator-jhipster-kotlin (CVE-2019-16303)

Summary

Vulnerability in generator-jhipster-kotlin (CVE-2019-16303). Successful exploitation can lead to full system takeover. Exploitable via RandomStringUtils. Mitigation: upgrade to 1.2.0 or later.

Original description

The description as published by the source.

Account takeover and privilege escalation is possible in applications generated by generator-jhipster before 6.3.0. This is due to a vulnerability in the generated java classes: CWE-338: Use of Cryptographically Weak Pseudo-Random Number Generator (PRNG)

Generated applications must be manually patched, following instructions in the release notes: https://www.jhipster.tech/2019/09/13/jhipster-release-6.3.0.html

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2019-16303 has been found in generator-jhipster-kotlin.
Attackers can target a specific entry point like RandomStringUtils over the network to misuse the product.
Successful exploitation can lead to full system takeover.
What to do: upgrade generator-jhipster-kotlin to 1.2.0 or later.
If unsure, ask your IT team or search "generator-jhipster-kotlin CVE-2019-16303" on the vendor's site.

CVE-2019-16303 (generator-jhipster-kotlin) — CWE-338
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: RandomStringUtils / RandomUtil.kt / RandomStringUtils.randomAlphaNumeric
Patched: 1.2.0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-338) exists in generator-jhipster-kotlin. Attackers reach the vulnerable code path via RandomStringUtils without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of generator-jhipster-kotlin. Attack surface: RandomStringUtils / RandomUtil.kt / RandomStringUtils.randomAlphaNumeric.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.2.0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'generator-jhipster-kotlin' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'generator-jhipster-kotlin' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で generator-jhipster-kotlin を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade generator-jhipster-kotlin to 1.2.0

    ステージング環境で 1.2.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm generator-jhipster-kotlin
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.2.0"}]}]
npm generator-jhipster
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"6.3.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details