Skip to content

GHSA-fv48-hjhp-94c7 CVE-2020-12477

Incorrect Authorization in TeamPass

High Packagist
Severity
7.5 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.80%
Chance of exploitation in the next 30 days. Higher than 78.53% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-863 Incorrect Authorization
Fix
None yet
No fixed version published

Description

The REST API functions in TeamPass 2.1.27.36 allow any user with a valid API token to bypass IP address whitelist restrictions via an X-Forwarded-For client HTTP header to the getIp function.

Affected versions

Packagist

PackageVulnerableFixed in
nilsteampassnet/teampass
<= 2.1.27.36
No fix yet

How to fix

No fixed version has been published yet. Until one is, remove or replace the package, or turn off or isolate the affected feature. This page updates when a fix ships.

Severity breakdown

CVSS 3.1 7.5

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

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

Weakness

CWE-863: Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

How to prevent it
  • Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
  • Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
  • Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
  • Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
  • System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

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