CVE-2019-3803: Concourse includes token in CLI authentication callback
First published: Thu Jan 10 2019(Updated: )
Pivotal Concourse, all versions prior to 4.2.2, puts the user access token in a url during the login flow. A remote attacker who gains access to a user's browser history could obtain the access token and use it to authenticate as the user.
Credit: security_alert@emc.com security_alert@emc.com
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Pivotal Software Concourse | <4.2.2 | |
| <4.2.2 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2019-3803?
CVE-2019-3803 is a vulnerability in Pivotal Concourse versions prior to 4.2.2 that allows a remote attacker to obtain a user's access token from the browser history.
How does CVE-2019-3803 affect Pivotal Concourse?
CVE-2019-3803 affects Pivotal Concourse versions prior to 4.2.2.
What is the severity of CVE-2019-3803?
CVE-2019-3803 is considered high severity with a severity value of 7.5.
How can a remote attacker exploit CVE-2019-3803?
A remote attacker can gain access to a user's browser history to obtain the access token and authenticate as the user.
Is there a fix available for CVE-2019-3803?
Yes, the fix for CVE-2019-3803 is to update Pivotal Concourse to version 4.2.2 or later.
- collector/nvd-index
- agent/type
- agent/references
- agent/severity
- agent/weakness
- agent/title
- agent/description
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- collector/nvd-api
- source/NVD
- agent/software-canonical-lookup
- agent/author
- agent/last-modified-date
- agent/softwarecombine
- agent/tags
- agent/event
- vendor/pivotal software
- canonical/pivotal software concourse