[MNG-5992] Git passwords are exposed as the Super POM still uses Maven Release Plugin 2.3.2

• Type: Improvement
• Status: Closed
• Priority: Critical
• Resolution: Fixed
• Affects Version/s: 3.3.3, 3.3.9
• Fix Version/s: 3.5.3
• Component/s: Bootstrap & Build, Plugins and Lifecycle, POM
• Labels: security
• Environment: All
• Assignee: Herve Boutemy
• Reporter: Ryan J. McDonough
• Created: 27/Mar/16 23:23
• Updated: 28/Mar/20 15:02
• Resolved: 08/Feb/18 21:50

Description

The super POM defines version 2.3.2 of the Maven Release plugin. When using HTTP/HTTPS Git SCM URIs, Maven will printout the password in the logs. Thus, any CI system such as Jenkins, TravisCI, etc. will have the passwords exposed in the logs and in the console output. In the case of TravisCI, this will be publicly visible.

The Maven Release Plugin fixed this issue in MRELEASE-846, but Maven core is still pointing at an exposed version of the Maven Release plugin. I have a test case that demonstrates the issue here:

https://github.com/damnhandy/maven-publish-issue

If you run the same build and explicitly define 2.5.3, the password is no longer displayed. This should be the default.

Issue Links

• is superceded by: MNG-6054 Remove super POM plugin management section
• links to: GitHub Pull Request #152