JLLeitschuh opened a new pull request, #21:
URL: https://github.com/apache/logging-log4j1/pull/21

   
[![mitm_build](https://user-images.githubusercontent.com/1323708/59226671-90645200-8ba1-11e9-8ab3-39292bef99e9.jpeg)](https://medium.com/@jonathan.leitschuh/want-to-take-over-the-java-ecosystem-all-you-need-is-a-mitm-1fc329d898fb?source=friends_link&sk=3c99970c55a899ad9ef41f126efcde0e)
   
   ---
   
   This is a security fix for a high severity vulnerability in your [Apache 
Maven](https://maven.apache.org/) `pom.xml` file(s).
   
   The build files indicate that this project is resolving dependencies over 
HTTP instead of HTTPS.
   This leaves your build vulnerable to allowing a [Man in the 
Middle](https://en.wikipedia.org/wiki/Man-in-the-middle_attack) (MITM) 
attackers to execute arbitrary code on your or your computer or CI/CD system.
   
   This vulnerability has a CVSS v3.0 Base Score of 
[8.1/10](https://nvd.nist.gov/vuln-metrics/cvss/v3-calculator?vector=AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H).
   
   [POC 
code](https://max.computer/blog/how-to-take-over-the-computer-of-any-java-or-clojure-or-scala-developer/)
 has existed since 2014 to maliciously compromise a JAR file in-flight.
   MITM attacks against HTTP are [increasingly 
common](https://security.stackexchange.com/a/12050), for example [Comcast is 
known to have done it to their own 
users](https://thenextweb.com/insights/2017/12/11/comcast-continues-to-inject-its-own-code-into-websites-you-visit/#).
   
   This contribution is a part of a submission to the [GitHub Security 
Lab](https://securitylab.github.com/) Bug Bounty program.
   
   ## Resources
   
   - [Want to take over the Java ecosystem? All you need is a 
MITM!](https://medium.com/@jonathan.leitschuh/want-to-take-over-the-java-ecosystem-all-you-need-is-a-mitm-1fc329d898fb?source=friends_link&sk=3c99970c55a899ad9ef41f126efcde0e)
   - [Update: Want to take over the Java ecosystem? All you need is a 
MITM!](https://medium.com/bugbountywriteup/update-want-to-take-over-the-java-ecosystem-all-you-need-is-a-mitm-d069d253fe23?source=friends_link&sk=8c8e52a7d57b98d0b7e541665688b454)
   - [CVE-2021-26291](https://nvd.nist.gov/vuln/detail/CVE-2021-26291)
   
   ## Detecting this and Future Vulnerabilities
   
   This vulnerability was automatically detected by GitHub's 
[LGTM.com](https://lgtm.com) using this [CodeQL 
Query](https://lgtm.com/rules/1511115648721/).
   
   You can automatically detect future vulnerabilities like this by enabling 
the free (for open-source) [GitHub 
Action](https://github.com/github/codeql-action).
   
   I'm not an employee of GitHub, I'm simply an open-source security researcher.
   
   ## Source
   
   This contribution was automatically generated with an 
[OpenRewrite](https://github.com/openrewrite/rewrite) [refactoring 
recipe](https://docs.openrewrite.org/), which was lovingly hand crafted to 
bring this security fix to your repository.
   
   The source code that generated this PR can be found here:
   
[UseHttpsForRepositories](https://github.com/openrewrite/rewrite/blob/f8c139d0d66ad9a60ee73b95b7a79571e4820769/rewrite-maven/src/main/java/org/openrewrite/maven/security/UseHttpsForRepositories.java)
   
   ## Opting-Out
   
   If you'd like to opt-out of future automated security vulnerability fixes 
like this, please consider adding a file called
   `.github/GH-ROBOTS.txt` to your repository with the line:
   
   ```
   User-agent: JLLeitschuh/security-research
   Disallow: *
   ```
   
   This bot will respect the [ROBOTS.txt](https://moz.com/learn/seo/robotstxt) 
format for future contributions.
   
   Alternatively, if this project is no longer actively maintained, consider 
[archiving](https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-archiving-repositories)
 the repository.
   
   ## CLA Requirements
   
   _This section is only relevant if your project requires contributors to sign 
a Contributor License Agreement (CLA) for external contributions._
   
   It is unlikely that I'll be able to directly sign CLAs. However, all 
contributed commits are already automatically signed-off.
   
   > The meaning of a signoff depends on the project, but it typically 
certifies that committer has the rights to submit this work under the same 
license and agrees to a Developer Certificate of Origin 
   > (see 
[https://developercertificate.org/](https://developercertificate.org/) for more 
information).
   >
   > \- [Git Commit Signoff documentation](https://developercertificate.org/)
   
   If signing your organization's CLA is a strict-requirement for merging this 
contribution, please feel free to close this PR.
   
   ## Sponsorship & Support
   
   This contribution is sponsored by HUMAN Security Inc. and the new Dan 
Kaminsky Fellowship, a fellowship created to celebrate Dan's memory and legacy 
by funding open-source work that makes the world a better (and more secure) 
place.
   
   This PR was generated by [Moderne](https://www.moderne.io/), a free-for-open 
source SaaS offering that uses format-preserving AST transformations to fix 
bugs, standardize code style, apply best practices, migrate library versions, 
and fix common security vulnerabilties at scale.
   
   ## Tracking
   
   All PR's generated as part of this fix are tracked here: 
https://github.com/JLLeitschuh/security-research/issues/8


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: dev-unsubscr...@logging.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to