GHSA-pfxf-wh96-fvjc is a medium-severity (CVSS 5.3) CWE-117 vulnerability in generator-jhipster-kotlin. O3 Security confirms whether GHSA-pfxf-wh96-fvjc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Log Forging in generator-jhipster-kotlin
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
generator-jhipster-kotlinnpmDescription
Impact
We log the mail for invalid password reset attempts. As the email is provided by a user and the api is public this can be used by an attacker to forge log entries. This is vulnerable to https://cwe.mitre.org/data/definitions/117.html
This problem affects only application generated with jwt or session authentication. Applications using oauth are not vulnerable.
Patches
version 1.7.0.
Workarounds
In AccountResource.kt you should change the line
log.warn("Password reset requested for non existing mail '$mail'");
to
log.warn("Password reset requested for non existing mail");
References
- https://cwe.mitre.org/data/definitions/117.html
- https://owasp.org/www-community/attacks/Log_Injection
- https://www.baeldung.com/jvm-log-forging
For more information
If you have any questions or comments about this advisory:
- Open an issue in jhipster kotlin
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | generator-jhipster-kotlin | ≥ 1.6.0&&< 1.7.0 | 1.7.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for generator-jhipster-kotlin. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update generator-jhipster-kotlin to 1.7.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-pfxf-wh96-fvjc is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-pfxf-wh96-fvjc is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-pfxf-wh96-fvjc. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-pfxf-wh96-fvjc in your dependencies?
O3 detects GHSA-pfxf-wh96-fvjc across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.