What is CVE-2018-1000109?

CVE-2018-1000109 is a medium-severity incorrect authorization vulnerability in org.jenkins-ci.plugins:google-play-android-publisher (maven), affecting versions <= 1.6. It is fixed in 1.7. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.

How severe is CVE-2018-1000109?

CVE-2018-1000109 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.jenkins-ci.plugins:google-play-android-publisher are affected by CVE-2018-1000109?

org.jenkins-ci.plugins:google-play-android-publisher (maven) versions <= 1.6 is affected.

Is there a fix for CVE-2018-1000109?

Yes. CVE-2018-1000109 is fixed in 1.7. Upgrade to this version or later.

Is CVE-2018-1000109 exploitable, and should I be worried?

Whether CVE-2018-1000109 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2018-1000109 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2018-1000109

Q: How severe is CVE-2018-1000109?

CVE-2018-1000109 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Is there a fix for CVE-2018-1000109?

Yes. CVE-2018-1000109 is fixed in 1.7. Upgrade to this version or later.

Q: Is CVE-2018-1000109 exploitable, and should I be worried?

Whether CVE-2018-1000109 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2018-1000109 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2018-1000109?

Upgrade org.jenkins-ci.plugins:google-play-android-publisher to 1.7 or later.

Summary

Jenkins Google Play Android Publisher Plugin allows attacker to obtain credential IDs

An improper authorization vulnerability exists in Jenkins Google Play Android Publisher Plugin version 1.6 and earlier in GooglePlayBuildStepDescriptor.java that allow an attacker to obtain credential IDs. As of version 1.7, enumeration of credentials IDs and validation of specified credentials in this plugin requires the permissions to have the ExtendedRead permission (when that permission is enabled; otherwise Configure permission) to the job in whose context credentials are being accessed.

Impact

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2018-1000109 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.7); upgrading removes the vulnerable code path.

Affected versions

org.jenkins-ci.plugins:google-play-android-publisher (<= 1.6)

Security releases

org.jenkins-ci.plugins:google-play-android-publisher → 1.7 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade org.jenkins-ci.plugins:google-play-android-publisher to 1.7 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2018-1000109? CVE-2018-1000109 is a medium-severity incorrect authorization vulnerability in org.jenkins-ci.plugins:google-play-android-publisher (maven), affecting versions <= 1.6. It is fixed in 1.7. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
How severe is CVE-2018-1000109? CVE-2018-1000109 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.jenkins-ci.plugins:google-play-android-publisher are affected by CVE-2018-1000109? org.jenkins-ci.plugins:google-play-android-publisher (maven) versions <= 1.6 is affected.
Is there a fix for CVE-2018-1000109? Yes. CVE-2018-1000109 is fixed in 1.7. Upgrade to this version or later.
Is CVE-2018-1000109 exploitable, and should I be worried? Whether CVE-2018-1000109 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2018-1000109 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2018-1000109? Upgrade org.jenkins-ci.plugins:google-play-android-publisher to 1.7 or later.