Skip to content

Log Forging in generator-jhipster-kotlin

Moderate severity GitHub Reviewed Published Jun 23, 2020 in jhipster/jhipster-kotlin • Updated Jan 9, 2023

Package

npm generator-jhipster-kotlin (npm)

Affected versions

= 1.6.0

Patched versions

1.7.0

Description

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

For more information

If you have any questions or comments about this advisory:

References

@sendilkumarn sendilkumarn published to jhipster/jhipster-kotlin Jun 23, 2020
Reviewed Jun 25, 2020
Published to the GitHub Advisory Database Jun 25, 2020
Last updated Jan 9, 2023

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

EPSS score

0.223%
(61st percentile)

Weaknesses

CVE ID

CVE-2020-4072

GHSA ID

GHSA-pfxf-wh96-fvjc

Source code

No known source code
Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.