Release notes
*Sourced from [git-commit-id-plugin's releases](https://github.com/ktoso/maven-git-commit-id-plugin/releases).*
> 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://github-redirect.dependabot.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-redirect.dependabot.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-redirect.dependabot.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://github-redirect.dependabot.com/ktoso/maven-git-commit-id-plugin/issues)
Commits
- [`16f5f00`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/16f5f00a38db44e913ed538bd3f6c3d6b76da9be) [maven-release-plugin] prepare release v2.2.6
- [`69f93bc`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/69f93bc566f553438d19310cda55c986bb6cbb01) [maven-release-plugin] prepare for next development iteration
- [`30e7a5d`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/30e7a5d6af82806cade33dd62511a3dc1e186aa0) use openjdk for tests (sick of the random travis failures due to oraclejdk be...
- [`bf4cece`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/bf4cece2cd105d939351cab0b3a7cb84e26a520e) update jackson-databind to v2.9.8 in response to https://github.com/FasterXML...
- See full diff in [compare view](https://github.com/ktoso/maven-git-commit-id-plugin/compare/v2.2.5...v2.2.6)
Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.
Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
- `@dependabot rebase` will rebase this PR
- `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it
- `@dependabot merge` will merge this PR after your CI passes on it
- `@dependabot cancel merge` will cancel a previously requested merge
- `@dependabot reopen` will reopen this PR if it is closed
- `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself)
- `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
- `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language
- `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language
- `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language
- `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language
- `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme
Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com):
- Update frequency (including time of day and day of week)
- Automerge options (never/patch/minor, and dev/runtime dependencies)
- Pull request limits (per update run and/or open at any time)
- Out-of-range updates (receive only lockfile updates, if desired)
- Security updates (receive only security updates, if desired)
Finally, you can contact us by mentioning @dependabot.
Bumps git-commit-id-plugin from 2.2.5 to 2.2.6.
Release notes
*Sourced from [git-commit-id-plugin's releases](https://github.com/ktoso/maven-git-commit-id-plugin/releases).* > 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://github-redirect.dependabot.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-redirect.dependabot.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 `Commits
- [`16f5f00`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/16f5f00a38db44e913ed538bd3f6c3d6b76da9be) [maven-release-plugin] prepare release v2.2.6 - [`69f93bc`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/69f93bc566f553438d19310cda55c986bb6cbb01) [maven-release-plugin] prepare for next development iteration - [`30e7a5d`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/30e7a5d6af82806cade33dd62511a3dc1e186aa0) use openjdk for tests (sick of the random travis failures due to oraclejdk be... - [`bf4cece`](https://github.com/git-commit-id/maven-git-commit-id-plugin/commit/bf4cece2cd105d939351cab0b3a7cb84e26a520e) update jackson-databind to v2.9.8 in response to https://github.com/FasterXML... - See full diff in [compare view](https://github.com/ktoso/maven-git-commit-id-plugin/compare/v2.2.5...v2.2.6)Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.