Red Hat Security Advisory: OpenShift Container Platform 4.17.35 bug fix and security update

1. Implementation

   When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.

2. Architecture and Design

   Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly.

3. Architecture and Design · Operation · Sandbox or Jail

   Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software.

OWASP Cheat Sheets

• REST Assessment (opens in a new tab)
• Authorization (opens in a new tab)

OWASP ASVS 4.0.3

• V4.3.3 (opens in a new tab)
• V8.3.8 (opens in a new tab)
• V13.4.2 (opens in a new tab)

Attack patterns

• Accessing Functionality Not Properly Constrained by ACLs (opens in a new tab)
• Directory Indexing (opens in a new tab)
• Using Malicious Files (opens in a new tab)
• Exploiting Incorrectly Configured Access Control Security Levels (opens in a new tab)
• Signing Malicious Code (opens in a new tab)

From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

1. Architecture and Design · Implementation · Attack Surface Reduction

   Hard-code the search path to a set of known-safe values (such as system directories), or only allow them to be specified by the administrator in a configuration file. Do not allow these settings to be modified by an external party. Be careful to avoid related weaknesses such as CWE-426 and CWE-428.

2. Implementation

   When invoking other programs, specify those programs using fully-qualified pathnames. While this is an effective approach, code that uses fully-qualified pathnames might not be portable to other systems that do not use the same pathnames.

3. Implementation

   Remove or restrict all environment settings before invoking other programs. This includes the PATH environment variable, LD_LIBRARY_PATH, and other settings that identify the location of code libraries, and any application-specific search paths.

OWASP Cheat Sheets

• Software Supply Chain Security (opens in a new tab)
• Infrastructure as Code (opens in a new tab)

Attack patterns

• Leveraging/Manipulating Configuration File Search Paths (opens in a new tab)

From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

1. Implementation · Input Validation

   Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.

OWASP Cheat Sheets

• XML Security (opens in a new tab)
• Mass Assignment (opens in a new tab)

OWASP ASVS 4.0.3

• V13.3.1 (opens in a new tab)
• V5.1.4 (opens in a new tab)
• V5.1.3 (opens in a new tab)

Attack patterns

• SQL Injection (opens in a new tab)
• NoSQL Injection (opens in a new tab)

From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

1. Implementation

   Use a web server that employs a strict HTTP parsing procedure, such as Apache.

2. Implementation

   Use only SSL communication.

3. Implementation

   Terminate the client session after each request.

OWASP Cheat Sheets

• REST Assessment (opens in a new tab)
• REST Security (opens in a new tab)
• Cross-Site Request Forgery Prevention (opens in a new tab)
• Secure Design Principles (opens in a new tab)

OWASP ASVS 4.0.3

• V13.2.5 (opens in a new tab)

Attack patterns

• HTTP Response Smuggling (opens in a new tab)
• HTTP Request Smuggling (opens in a new tab)

From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).