Update dependency pl.project13.maven:git-commit-id-plugin to v2.2.6 - autoclosed

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
pl.project13.maven:git-commit-id-plugin (source)	2.2.5 -> 2.2.6

---

Release Notes

git-commit-id/git-commit-id-maven-plugin (pl.project13.maven:git-commit-id-plugin)

### [`v2.2.6`](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/releases/tag/v2.2.6): Version 2.2.6 [Compare Source](https://togithub.com/git-commit-id/git-commit-id-maven-plugin/compare/v2.2.5...v2.2.6) Version 2.2.6 is a security update for a potential issue within the jackson-databind dependency. As usual you can checkout the detailed list of [bug-fixes](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues?q=milestone%3A2.2.6\&closed=1) :-) #### New Features / Bug-Fixes: The main key-aspects is a security update for a potential issue within the jackson-databind dependency. This specific dependency was updated to v2.9.8 in response to [https://github.com/FasterXML/jackson-databind/issues/2186](https://togithub.com/FasterXML/jackson-databind/issues/2186) (CVE-2018-19360, CVE-2018-19361, CVE-2018-19362). Even though **by default** an user of this plugin **does not seem to be affected** by this potential issue, it is highly recommended to adopt the latest version at your earliest convenience. Similar to version 2.2.5 this version provides full support for Java 7, Java 8, Java 9, Java 10 and Java 11 (and is potentially also working for any higher version). #### Am I affected? (technical details) The specific issues that have been fixed with the update of jackson-databind dependency are: - [CVE-2018-19360](https://nvd.nist.gov/vuln/detail/CVE-2018-19360): FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the axis2-transport-jms class from polymorphic deserialization. - [CVE-2018-19361](https://nvd.nist.gov/vuln/detail/CVE-2018-19361): FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the openjpa class from polymorphic deserialization. - [CVE-2018-19362](https://nvd.nist.gov/vuln/detail/CVE-2018-19362): FasterXML jackson-databind 2.x before 2.9.8 might allow attackers to have unspecified impact by leveraging failure to block the jboss-common-core class from polymorphic deserialization. This plugin uses the jackson-databind dependency for dumping the git information (serialization) to the generated properties file and determining if the generated json properties are up-to-date (deserialization). As of now it appears that **only** user who **generate json properties** via `json` may be affected by those issues. This specific configuration is set to `properties` by default and hence by default it appears that those issues are out of scope. Only when this configuration is altered a user may need to consider the linked CVE's as potential security problem. In general I would be unsure if this ever even could be considered a true attack vector of this plugin, since the generated json file would need to contain data that would trigger this specific bug in the dependency. If an adversary has access to the content to the location where the generated file is residing, I would assume he can also modify the any local file (including project files) and hence would not need to go through the pain and exploit this problem.... #### Getting the latest release The plugin is available from Maven Central ([see here](http://search.maven.org/#search%7Cga%7C1%7Cpl.project13)), so you don't have to configure any additional repositories to use this plugin. All you need to do is to configure it inside your project as dependency: ```xml pl.project13.maven git-commit-id-plugin 2.2.6 ``` #### Known Issues / Limitations: - This plugin is unfortunately not working with Heroku which is due to the fact how Heroku works. In summary Heroku does not copy over the .git-repository but in order to determine the git properties this plugin relies on the fact that it has access to the git-repository. A somewhat *workaround* to get some information is outlined in [https://github.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues/279#issuecomment-301284022) #### Reporting Problems If you find any problem with this plugin, feel free to report it [here](https://togithub.com/ktoso/maven-git-commit-id-plugin/issues)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.