Is This vulnerability exploited in the wild?

No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.

How severe is This vulnerability?

Low severity, with a CVSS score of 3.1, published 23 September 2019.

Which products and versions are affected?

generator-jhipster (npm) SEMVER:introduced=0,fixed=6.3.1.

Is there a fix for This vulnerability?

Yes. generator-jhipster (npm): upgrade to 6.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is This vulnerability attacked?

It is attacked over the network or from the adjacent network.

Check whether you run generator-jhipster (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

JHipster generator HTTP repository configuration in generated code

Severity: low · CVSS 3.1 · Published 2019-09-23

JHipster is a popular development tool that generates Java web application scaffolding. The generated build configuration files incorrectly default to downloading dependencies over unencrypted HTTP instead of HTTPS, allowing attackers on the same network to intercept and replace those dependencies with malicious code during the build process. This could lead to compromise of any application built with an affected version.

Technologies: generator-jhipster (npm). Vendors: npm.

Quick answers

Is This vulnerability exploited in the wild?: No. Junglewise Threat Intelligence has no report of This vulnerability being exploited in the wild.
How severe is This vulnerability?: Low severity, with a CVSS score of 3.1, published 23 September 2019.
Which products and versions are affected?: generator-jhipster (npm) SEMVER:introduced=0,fixed=6.3.1.
Is there a fix for This vulnerability?: Yes. generator-jhipster (npm): upgrade to 6.3.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is This vulnerability attacked?: It is attacked over the network or from the adjacent network.
Am I affected?: Check whether you run generator-jhipster (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

generator-jhipster (npm): upgrade to 6.3.1 or later
```
npm install generator-jhipster@6.3.1
```

Technical details

The vulnerability is a case of CWE-494 (download without integrity check) and CWE-829 (untrusted functionality inclusion) in generated Maven and Gradle build files. JHipster generates build configuration that references Maven Central repositories using HTTP instead of HTTPS, specifically the Spring plugin repository at http://repo.spring.io/plugins-release. An attacker positioned on the network path between the developer's build machine and the repository can perform a man-in-the-middle attack to serve malicious artifacts. This attack requires no special privileges or user interaction, though the attacker must have network positioning (intermediate routing). Maven users are affected up to version 6.3.0; Gradle users up to 6.3.1. The fix updates generated repository URLs to use HTTPS.

Affected products

JHipster generator-jhipster <6.3.1

Timeline

2019-09-20: disclosed
2019-09-20: patched: Maven users: 6.3.0; Gradle users: 6.3.1

References

https://github.com/jhipster/generator-jhipster/security/advisories/GHSA-mc84-xr9p-938r

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.