Skip to content

GHSA-q99w-j4mj-7hj8 CVE-2018-20028

Contao Information Disclosure via Access Control Flaws

Medium Packagist
Severity
6.5 / 10
Medium · CVSS 3.0
Exploit chance (EPSS)
0.91%
Chance of exploitation in the next 30 days. Higher than 59.88% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-284 Improper Access Control
Fix
3.5.37
Upgrade contao/contao to this version or later

Description

Contao 3.x before 3.5.37, 4.4.x before 4.4.31 and 4.6.x before 4.6.11 has Incorrect Access Control.

Affected versions

Packagist

PackageVulnerableFixed in
contao/contao
>= 3.0.0, < 3.5.37
3.5.37
contao/contao
>= 4.6.0, < 4.6.11
4.6.11
contao/contao
>= 4.4.0, < 4.4.31
4.4.31

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 → 3.5.37

composer
composer require contao/contao:^3.5.37

Severity breakdown

CVSS 3.0 6.5

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

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

Weakness

CWE-284: Improper Access Control

The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.

How to prevent it
  • Architecture and Design, Operation: Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
  • Architecture and Design: Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area. Ensure that appropriate compartmentalization is built into the system design, and the compartmentalization allows for and reinforces privilege separation functionality. Architects and designers should rely on the principle of least privilege to decide the appropriate time to use privileges and the time to drop privileges.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
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
GHSA-3mr9-p497-58f6
Contao crawler leaks auth credentials to external hosts
Low Also affects contao/contao
GHSA-qqfq-7cpp-hcqj
Contao does not properly manage privileges for page and article fields
Medium Also affects contao/contao
GHSA-w53m-gxvg-vx7p
Contao can disclose sensitive information in the news module
Medium Also affects contao/contao
GHSA-2xmj-8wmq-7475
Contao discloses sensitive information in the front end search index
Medium Also affects contao/contao
GHSA-7m47-r75r-cx8v
Contao applies improper access control in the back end voters
Medium Also affects contao/contao
GHSA-fp7q-xhhw-6rj3
Path traversal vulnerability in the file manager
Medium 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