Skip to content

GHSA-xvjf-394g-phrr CVE-2017-15053

TeamPass Improper Privilege Management

Medium Packagist
Severity
4.9 / 10
Medium · CVSS 3.0
Exploit chance (EPSS)
0.92%
Chance of exploitation in the next 30 days. Higher than 60.22% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-269 Improper Privilege Management
Fix
2.1.27.9
Upgrade nilsteampassnet/teampass to this version or later

Description

TeamPass before 2.1.27.9 does not properly enforce manager access control when requesting roles.queries.php. It is then possible for a manager user to modify any arbitrary roles within the application, or delete any arbitrary role. To exploit the vulnerability, an authenticated attacker must have the manager rights on the application, then tamper with the requests sent directly, for example by changing the "id" parameter when invoking "delete_role" on roles.queries.php.

Affected versions

Packagist

PackageVulnerableFixed in
nilsteampassnet/teampass
< 2.1.27.9
2.1.27.9

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.

nilsteampassnet/teampass Packagist → 2.1.27.9

composer
composer require nilsteampassnet/teampass:^2.1.27.9

Severity breakdown

CVSS 3.0 4.9

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

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

Weakness

CWE-269: Improper Privilege Management

The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that 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: Follow the principle of least privilege when assigning access rights to entities in a software system.
  • Architecture and Design: Consider following the principle of separation of privilege. Require multiple conditions to be met before permitting access to a system resource.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-9wmc-988h-2mv2
TeamPass privileges issue
High Also affects nilsteampassnet/teampass
GHSA-7rm3-4w6j-8xx4
TeamPass mail_me operation authorization issue
Medium Also affects nilsteampassnet/teampass
GHSA-2697-96mv-3gfm
TeamPass does not properly check whether a folder is in a user's allowed folders list
Medium Also affects nilsteampassnet/teampass
GHSA-524r-w8fx-hqg3
TeamPass Cross-site Scripting vulnerability
Medium Also affects nilsteampassnet/teampass
GHSA-2rhg-hqq9-8xjh
TeamPass information exposure vulnerability
High Also affects nilsteampassnet/teampass
GHSA-2cv5-qvq3-6276
TeamPass vulnerable to Improper Encoding or Escaping of Output
Medium Also affects nilsteampassnet/teampass
GHSA-97hm-2mfr-2p97
TeamPass Code Injection vulnerability
High Also affects nilsteampassnet/teampass
GHSA-pwrw-g29q-3mp8
TeamPass Cross-site Scripting vulnerability
Medium Also affects nilsteampassnet/teampass
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