GHSA-8w7w-67mw-r5p7
generator-jhipster vulnerable to login check Regular Expression Denial of Service
GHSA-8w7w-67mw-r5p7 is a vulnerability with no CVSS score yet in generator-jhipster, published October 6, 2022. No source lists public exploit code. No source names a fixed version.
- Severity
- UnratedNo CVSS score yet
- Exploit chance
- UnscoredNo EPSS score yet
- Exploitation
- None knownNot on CISA’s or ENISA’s lists
- Fixed in
- No fix listedNo source names one
Description
Impact
For applications using JWT or session-based authentication (not OIDC), users can input a login string which can cause a denial of service, as parsing it will be too complex.
Here is an example: https://gist.github.com/atomfrede/311f8a9c6eb74c5c5226af0481155207
The vulnerable expression was never officially released. So only when you generated an application from the master branch between 6.8.0 and 6.9.0 your generated application may be vulnerable.
Patches
If you only used official releases you don't need to patch your application.
Workarounds
If you have created an application from the master branch, you need to adapt the LOGIN_REGEX in Constants.java. If your regex is
^[a-zA-Z0-9!#$&'*+=?^_`{|}~.-]+@?[a-zA-Z0-9-]+(?:\\.[a-zA-Z0-9-]+)*$
you need to change it too
^(?>[a-zA-Z0-9!$&*+=?^_`{|}~.-]+@[a-zA-Z0-9-]+(?:\\.[a-zA-Z0-9-]+)*)|(?>[_.@A-Za-z0-9-]+)$
If you still have ^[_.@A-Za-z0-9-]*$ there is no need to change it, except you would like to support login with + sign (e.g. foo+bar@example.com).
References
Affected packages
| Package | Affected | Fixed |
|---|---|---|
generator-jhipsternpm | Source text: > 6.8.0, < 6.9.0 | Not evaluated |
Not evaluated means the source gave git commits or a range we can't read, so we can't tell which releases are affected. A fixed version beside it is the source’s own claim.
What each source reports
GitHub AdvisoriesNo score
generator-jhipster vulnerable to login check Regular Expression Denial of Service
Impact
For applications using JWT or session-based authentication (not OIDC), users can input a login string which can cause a denial of service, as parsing it will be too complex.
Here is an example: https://gist.github.com/atomfrede/311f8a9c6eb74c5c5226af0481155207
The vulnerable expression was never officially released. So only when you generated an application from the master branch between 6.8.0 and 6.9.0 your generated application may be vulnerable.
Patches
If you only used official releases you don't need to patch your application.
Workarounds
If you have created an application from the master branch, you need to adapt the LOGIN_REGEX in Constants.java. If your regex is
^[a-zA-Z0-9!#$&'*+=?^_`{|}~.-]+@?[a-zA-Z0-9-]+(?:\\.[a-zA-Z0-9-]+)*$
you need to change it too
^(?>[a-zA-Z0-9!$&*+=?^_`{|}~.-]+@[a-zA-Z0-9-]+(?:\\.[a-zA-Z0-9-]+)*)|(?>[_.@A-Za-z0-9-]+)$
If you still have ^[_.@A-Za-z0-9-]*$ there is no need to change it, except you would like to support login with + sign (e.g. foo+bar@example.com).
References
- Record
GHSA-8w7w-67mw-r5p7- Updated
- 2026-11-02
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories |
Dates are when Every CVE recorded each change. Upstream dates may differ.