CyberSecBulletin
CVE-2023-4853NVD status: Modified

Openshift Serverless 1 on RHEL 8: Incorrect Authorization

Published Updated By the CyberSecBulletin desk

CVE-2023-4853 is a high-severity incorrect authorization vulnerability in Openshift Serverless 1 on RHEL 8 from Red Hat, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. There is no confirmed exploitation so far. EPSS estimates a 2.28% chance of exploitation within 30 days, higher than 83% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Quarkus to 2.16.11 or 3.2.6 or 3.3.3, whichever matches your release line, or a later version.
  2. Update Build Of Quarkus to 2.13.8 or a later version.
  3. Update Integration Camel K to 1.10.2 or a later version.
  4. Read the advisory on access.redhat.com for workarounds and exact fixed builds.
  5. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.

Affected products and versions

VendorProductAffected versionsFixed in
Red HatOpenshift Serverless 1 on RHEL 8Not specified in the recordNot stated
Red HatRed Hat build of OptaPlanner 8Not specified in the recordNot stated
Red HatRed Hat build of Quarkus 2.13.8.SP2Not specified in the recordNot stated
Red HatRed Hat Camel Extensions for Quarkus 2.13.3-1Not specified in the recordNot stated
Red HatRed Hat OpenShift Serverless 1.30Not specified in the recordNot stated
Red HatRHEL-8 based Middleware ContainersNot specified in the recordNot stated
Red HatRHINT Camel-K-1.10.2Not specified in the recordNot stated
Red HatRHINT Service Registry 2.5.4 GANot specified in the recordNot stated
Red HatRHPAM 7.13.4 asyncNot specified in the recordNot stated
Red HatRed Hat build of QuarkusNot specified in the recordNot stated
Red HatRed Hat Integration Camel Quarkus 2Not specified in the recordNot stated
Red HatRed Hat Process Automation 7Not specified in the recordNot stated
QuarkusQuarkusbefore 2.16.11; 3.2.0 up to, but not including, 3.2.6; 3.3.0 up to, but not including, 3.3.32.16.11, 3.2.6, 3.3.3
Red HatBuild Of Optaplanner8.0Not stated
Red HatBuild Of Quarkus2.13.0 up to, but not including, 2.13.82.13.8
Red HatDecision Manager7.0Not stated
Red HatIntegration Camel Kbefore 1.10.21.10.2
Red HatIntegration Camel QuarkusNot specified in the recordNot stated
Red HatIntegration Service RegistryNot specified in the recordNot stated
Red HatJboss Middleware1Not stated
Red HatJboss Middleware Text-only Advisories1.0Not stated
Red HatOpenshift Serverless1.0Not stated
Red HatProcess Automation Manager7.0Not stated
Red HatOpenshift Container Platform4.10; 4.11; 4.12Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
HighSuccess depends on conditions outside the attacker's control.
Privileges required
NoneNo account or login is needed.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.1HighCNA (redhat.com)
CVSS 3.18.1HighNVD

Official description

A flaw was found in Quarkus where HTTP security policies are not sanitizing certain character permutations correctly when accepting requests, resulting in incorrect evaluation of permissions. This issue could allow an attacker to bypass the security policy altogether, resulting in unauthorized endpoint access and possibly a denial of service.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: 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 developers prevent this class of flaw

  • 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) 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.
  • 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.
  • 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 and the OWASP ESAPI Access Control feature.

More Incorrect Authorization vulnerabilities (CWE-863)

Timeline

  1. CVE record published.
  2. Record last changed materially (score, affected products, status or references).

References

Recent Incorrect Authorization vulnerabilities

Spotted an error? Tell us.