Skip to content

GHSA-j99g-qjvx-995g CVE-2019-10643

Contao Does Not Expire Tokens Correctly

Critical Packagist
Severity
9.8 / 10
Critical · CVSS 3.0
Exploit chance (EPSS)
1.25%
Chance of exploitation in the next 30 days. Higher than 69.49% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-287 Improper Authentication
CWE-324 Use of a Key Past its Expiration Date
Fix
Available
2 packages have a fixed version

Description

Security researcher Ali Razzaq has discovered that confirming an opt-in token does not invalidate previous opt-in tokens in Contao 4.7.

Affected versions

Packagist

PackageVulnerableFixed in
contao/contao
>= 4.7.0, < 4.7.3
4.7.3
contao/core-bundle
>= 4.7.0, < 4.7.3
4.7.3

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

contao/contao Packagist → 4.7.3

composer
composer require contao/contao:^4.7.3

contao/core-bundle Packagist → 4.7.3

composer
composer require contao/core-bundle:^4.7.3

Severity breakdown

CVSS 3.0 9.8

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-287: Improper Authentication

When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.

How to prevent it
  • Architecture and Design: Use an authentication framework or library such as the OWASP ESAPI Authentication feature.

CWE-324: Use of a Key Past its Expiration Date

The product uses a cryptographic key or password past its expiration date, which diminishes its safety significantly by increasing the timing window for cracking attacks against that key.

How to prevent it
  • Architecture and Design: Adequate consideration should be put in to the user interface in order to notify users previous to the key's expiration, to explain the importance of new key generation and to walk users through the process as painlessly as possible.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-9ff2-p842-45wq
Contao: Cross-site request forgery in custom backend actions
Low Also affects contao/core-bundle
GHSA-q6wp-fr43-gm9v
Contao: Improper access control in the preview links module
Medium Also affects contao/core-bundle
GHSA-5974-gfqc-wrcm
Contao: Improper access control in the table access voter
Medium Also affects contao/core-bundle
GHSA-mrvp-7wmx-5m4h
Contao: Path traversal in the images controller
Medium Also affects contao/core-bundle
GHSA-mfxh-vp55-7gc6
Contao: The registration module re-sends activation mails
Medium Also affects contao/core-bundle
GHSA-x2rp-9qf7-2fmq
Contao: Protected page content is disclosed to anonymous visitors after contao.search.index_protected is disabled
Medium Also affects contao/core-bundle
GHSA-grm4-wm43-9jh5
Contao: Possible path traversal in job download URIs
Low Also affects contao/contao
GHSA-87mg-5grr-rhwh
Contao: Server-Side Request Forgery (SSRF) via Unvalidated RSS Feed URL in Feed Reader Module
Low Also affects contao/contao
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor