[Security] Bump geode-core from 1.2.0 to 1.7.0

[dependabot-preview]

Bumps geode-core from 1.2.0 to 1.7.0. This update includes security fixes.

Vulnerabilities fixed

Sourced from The Sonatype OSS Index.

[CVE-2017-15693] Deserialization of Untrusted Data
In Apache Geode before v1.4.0, the Geode server stores application objects in serialized form. Certain cluster operations and API invocations cause these objects to be deserialized. A user with DATA:WRITE access to the cluster may be able to cause remote code execution if certain classes are present on the classpath.

Affected versions: < 1.4.0

Sourced from The Sonatype OSS Index.

[CVE-2017-9795] When an Apache Geode cluster before v1.3.0 is operating in secure mode, a user w...
When an Apache Geode cluster before v1.3.0 is operating in secure mode, a user with read access to specific regions within a Geode cluster may execute OQL queries that allow read and write access to objects within unauthorized regions. In addition a user could invoke methods that allow remote code execution.

Affected versions: < 1.3.0

Sourced from The Sonatype OSS Index.

[CVE-2017-15692] Deserialization of Untrusted Data
In Apache Geode before v1.4.0, the TcpServer within the Geode locator opens a network port that deserializes data. If an unprivileged user gains access to the Geode locator, they may be able to cause remote code execution if certain classes are present on the classpath.

Affected versions: < 1.4.0

Sourced from The Sonatype OSS Index.

[CVE-2017-12622] When an Apache Geode cluster before v1.3.0 is operating in secure mode and an au...
When an Apache Geode cluster before v1.3.0 is operating in secure mode and an authenticated user connects to a Geode cluster using the gfsh tool with HTTP, the user is able to obtain status information and control cluster members even without CLUSTER:MANAGE privileges.

Affected versions: < 1.3.0

Sourced from The Sonatype OSS Index.

[CVE-2017-9794] When a cluster is operating in secure mode, a user with read privileges for spec...
When a cluster is operating in secure mode, a user with read privileges for specific data regions can use the gfsh command line utility to execute queries. In Apache Geode before 1.2.1, the query results may contain data from another user's concurrently executing gfsh query, potentially revealing data that the user is not authorized to view.

Affected versions: <= 1.2.0

Sourced from The Sonatype OSS Index.

[CVE-2017-9796] When an Apache Geode cluster before v1.3.0 is operating in secure mode, a user w...
When an Apache Geode cluster before v1.3.0 is operating in secure mode, a user with read access to specific regions within a Geode cluster may execute OQL queries containing a region name as a bind parameter that allow read access to objects within unauthorized regions.

Affected versions: < 1.3.0

Sourced from The Sonatype OSS Index.

[CVE-2017-9797] When an Apache Geode cluster before v1.2.1 is operating in secure mode, an unaut...
When an Apache Geode cluster before v1.2.1 is operating in secure mode, an unauthenticated client can enter multi-user authentication mode and send metadata messages. These metadata operations could leak information about application data types. In addition, an attacker could perform a denial of service attack on the cluster.

Affected versions: <= 1.2.0

Commits

• 48061cd Force inclusion of all ci/** files to work around exclude name collision (#2528)
• dd78494 GEODE-3967: Cleaning up of revert issues (#2523)
• 38dd001 Revert "GEODE-3967: There're following 9 problems fixed here:"
• f9abdeb Revert two GEODE-5600 commits
• c3494e0 GEODE-5727: rework how ResultModel deal with file contents. (#2460)
• c637193 GEODE-5723: Don't publish to maven repo unless SNAPSHOT. (#2453)
• 4185fe8 Changed the version number of JARs
• 1da670c Changing the pre version to 1.6.0 from 1.7.0 in TxCommitMessageTest
• 00f68ba GCP instances dont like underscores either? Using hyphen (#2440)
• 94b5c15 GCP instances cannot have dots in the name (#2439)
• Additional commits viewable in compare view

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:

• 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.

[dependabot-preview]

Superseded by #127.