CVE-2015-5298: Jenkins Google Login Plugin - Client-side Request Modification

Summary

08/07/2022
Yes i
Moderate
6.5

CVE-2015-5298: The Google Login Plugin (versions 1.0 and 1.1) allows malicious anonymous users to authenticate successfully against Jenkins instances that are supposed to be locked down to a particular Google Apps domain through client... Affects org.jenkins-ci.plugins:google-login versions >= 1.0, < 1.2. Fixed in 1.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

The Jenkins Google Login Plugin is a Maven package (org.jenkins-ci.plugins:google-login) that provides authentication functionality for Jenkins instances using Google accounts. It allows users to log in to Jenkins using their Google credentials, providing a convenient and secure authentication method.

Vulnerability Detail

The Google Login Plugin versions 1.0 and 1.1 suffer from a vulnerability that allows anonymous users to authenticate successfully against Jenkins instances that are supposed to be restricted to a specific Google Apps domain. This vulnerability occurs due to a lack of proper server-side validation of authentication requests, allowing malicious users to modify client-side requests and bypass the intended domain restrictions. The impact of this vulnerability is that unauthorized users can gain access to Jenkins instances and potentially perform unauthorized actions.

How To Fix

Minimum fixed version

1.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There is no known workaround for this vulnerability. It is essential to apply the recommended fix by upgrading to the latest version of the Google Login Plugin.

Conclusion

The Jenkins Google Login Plugin versions 1.0 and 1.1 are vulnerable to client-side request modification, allowing unauthorized users to authenticate against restricted instances. To mitigate this vulnerability, it is crucial to upgrade to version 1.2 or later of the plugin. For further assistance with vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for org.jenkins-ci.plugins:google-login →

Share this vulnerability

FAQ

The Jenkins Google Login Plugin is a plugin that enables users to authenticate to Jenkins using their Google accounts.

Versions 1.0 and 1.1 of the Google Login Plugin are affected by this vulnerability.

The vulnerability allows unauthorized users to authenticate successfully against Jenkins instances that should be restricted to a specific Google Apps domain.

To fix this vulnerability, upgrade the Google Login Plugin to version 1.2 or later.

No, there is no known workaround. It is necessary to apply the recommended fix by upgrading the plugin.

Related vulnerabilities

Recent vulnerabilities recorded for org.jenkins-ci.plugins:google-login.

How To Fix

Minimum fixed version

1.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback