Vulnerabilities
Misconfiguration
Runtime Security
Compliance
CVE Vulnerabilities

CVE-2020-4976

Incorrect Default Permissions

Published: Mar 11, 2021 | Modified: Apr 12, 2021
CVSS 3.x
4.4
MEDIUM
Source:
NVD
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
CVSS 2.x
3.6 LOW
AV:L/AC:L/Au:N/C:P/I:P/A:N
RedHat/V2
RedHat/V3
Ubuntu
Additional information
NVDhttps://nvd.nist.gov/vuln/detail/CVE-2020-4976
CWEhttps://cwe.mitre.org/data/definitions/276.html

IBM DB2 for Linux, UNIX and Windows (includes DB2 Connect Server) 9.7, 10.1, 10.5, 11.1, and 11.5 could allow a local user to read and write specific files due to weak file permissions. IBM X-Force ID: 192469.

Weakness

During installation, installed file permissions are set to allow anyone to modify those files.

Affected Software

Name Vendor Start Version End Version
Db2 Ibm 11.1.0.0 (including) 11.1.4.6 (excluding)
Db2 Ibm 11.5 (including) 11.5.5.0 (excluding)
Db2 Ibm 9.7 (including) 9.7 (including)
Db2 Ibm 9.7-fp1 (including) 9.7-fp1 (including)
Db2 Ibm 9.7-fp10 (including) 9.7-fp10 (including)
Db2 Ibm 9.7-fp2 (including) 9.7-fp2 (including)
Db2 Ibm 9.7-fp3 (including) 9.7-fp3 (including)
Db2 Ibm 9.7-fp3a (including) 9.7-fp3a (including)
Db2 Ibm 9.7-fp4 (including) 9.7-fp4 (including)
Db2 Ibm 9.7-fp5 (including) 9.7-fp5 (including)
Db2 Ibm 9.7-fp6 (including) 9.7-fp6 (including)
Db2 Ibm 9.7-fp7 (including) 9.7-fp7 (including)
Db2 Ibm 9.7-fp8 (including) 9.7-fp8 (including)
Db2 Ibm 9.7-fp9 (including) 9.7-fp9 (including)
Db2 Ibm 9.7-fp9a (including) 9.7-fp9a (including)
Db2 Ibm 10.1 (including) 10.1 (including)
Db2 Ibm 10.1-fp1 (including) 10.1-fp1 (including)
Db2 Ibm 10.1-fp2 (including) 10.1-fp2 (including)
Db2 Ibm 10.1-fp3 (including) 10.1-fp3 (including)
Db2 Ibm 10.1-fp3a (including) 10.1-fp3a (including)
Db2 Ibm 10.1-fp4 (including) 10.1-fp4 (including)
Db2 Ibm 10.1-fp5 (including) 10.1-fp5 (including)
Db2 Ibm 10.5 (including) 10.5 (including)
Db2 Ibm 10.5-fp1 (including) 10.5-fp1 (including)
Db2 Ibm 10.5-fp2 (including) 10.5-fp2 (including)
Db2 Ibm 10.5-fp3 (including) 10.5-fp3 (including)
Db2 Ibm 10.5-fp3a (including) 10.5-fp3a (including)
Db2 Ibm 10.5-fp4 (including) 10.5-fp4 (including)
Db2 Ibm 10.5-fp5 (including) 10.5-fp5 (including)
Db2 Ibm 10.5-fp6 (including) 10.5-fp6 (including)
Db2 Ibm 10.5-fp7 (including) 10.5-fp7 (including)
Db2 Ibm 10.5-fp8 (including) 10.5-fp8 (including)
Db2 Ibm 10.5-fp9 (including) 10.5-fp9 (including)

Potential Mitigations

  • 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

Aqua Security is the largest pure-play cloud native security company, providing customers the freedom to innovate and run their businesses with minimal friction. The Aqua Cloud Native Security Platform provides prevention, detection, and response automation across the entire application lifecycle to secure the build, secure cloud infrastructure and secure running workloads wherever they are deployed.
Copyright © 2024 Aqua Security Software Ltd.   Privacy Policy | Terms of Use