First published: Wed Oct 19 2022(Updated: )
GitLab Plugin 1.5.35 and earlier does not use a constant-time comparison when checking whether the provided and expected webhook token are equal. This could potentially allow attackers to use statistical methods to obtain a valid webhook token. GitLab Plugin 1.5.36 uses a constant-time comparison when validating the webhook token.
Credit: jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com jenkinsci-cert@googlegroups.com
Affected Software | Affected Version | How to fix |
---|---|---|
maven/org.jenkins-ci.plugins:gitlab-plugin | <=1.5.35 | 1.5.36 |
Jenkins GitLab | <1.5.36 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2022-43411 is considered a high severity vulnerability due to its potential for compromising webhook security.
To fix CVE-2022-43411, upgrade the GitLab Plugin to version 1.5.36 or later.
CVE-2022-43411 affects Jenkins instances that use GitLab Plugin versions 1.5.35 and earlier.
CVE-2022-43411 involves insufficient security in the comparison of webhook tokens, allowing for potential token leakage.
Yes, CVE-2022-43411 can potentially allow attackers to gain unauthorized access through valid webhook tokens.