Skip to content

GHSA-fq4h-m3c8-8m2v CVE-2022-2063

Improper Privilege Management in NocoDB

High npm
Severity
8.8 / 10
High · CVSS 3.1
Exploit chance (EPSS)
1.37%
Chance of exploitation in the next 30 days. Higher than 71.96% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-269 Improper Privilege Management
Fix
0.91.8
Upgrade nocodb to this version or later

Description

Improper Privilege Management in GitHub repository nocodb/nocodb prior to 0.91.8.

Affected versions

npm

PackageVulnerableFixed in
nocodb
< 0.91.8
0.91.8

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.

nocodb npm → 0.91.8

npm
npm install nocodb@0.91.8
yarn
yarn add nocodb@0.91.8
pnpm
pnpm add nocodb@0.91.8

Severity breakdown

CVSS 3.1 8.8

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

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

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-hmcr-rmjq-47qr
NocoDB: Server-Side Request Forgery via Spreadsheet Import Endpoint
Medium Also affects nocodb
GHSA-h6vv-pcq8-7xm4
NocoDB: Server-Side Request Forgery via Base Migration URL
Medium Also affects nocodb
GHSA-6mhr-74x2-98v9
NocoDB: Stored Cross-Site Scripting via Secure Attachment
Medium Also affects nocodb
GHSA-r989-7g3j-wjhw
NocoDB: Refresh Tokens Persist Through Password Recovery
Medium Also affects nocodb
GHSA-gprh-27j3-g5h4
NocoDB: Server-Side Request Forgery via Spreadsheet Fetch URL
Medium Also affects nocodb
GHSA-g72g-r7m4-9x4g
NocoDB: OAuth Tokens Persist Through Security Events
Medium Also affects nocodb
GHSA-xxpj-q764-9r6q
NocoDB: Missing Ownership Check in MCP Attachment Read
Low Also affects nocodb
GHSA-hj85-ph9q-78jg
NocoDB: Stored Cross-Site Scripting via Form View Redirect URL
High Also affects nocodb
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