CyberSecBulletin
CVE-2022-4244NVD status: Analyzed

RHINT Camel-K-1.10.1: Improper Limitation of a Pathname to a Restricted Directory

CVE-2022-4244 is a high-severity improper limitation of a pathname to a restricted directory vulnerability in RHINT Camel-K-1.10.1 from Red Hat, with a CVSS 3.1 base score of 7.5 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 1.35% chance of exploitation within 30 days, higher than 72% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update Plexus-utils to 3.0.24 or a later version.
  2. Update Integration Camel K to 1.10.1 or a later version.
  3. 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 HatRHINT Camel-K-1.10.1Not specified in the recordNot stated
Red HatRHPAM 7.13.1 asyncNot specified in the recordNot stated
Red HatA-MQ Clients 2Not specified in the recordNot stated
Red HatRed Hat A-MQ OnlineNot specified in the recordNot stated
Red HatRed Hat build of Apache Camel for Spring BootNot specified in the recordNot stated
Red HatRed Hat build of QuarkusNot specified in the recordNot stated
Red HatRed Hat Data Grid 8Not specified in the recordNot stated
Red HatRed Hat Decision Manager 7Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 7Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 8Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated
Red HatRed Hat Integration Camel QuarkusNot specified in the recordNot stated
Red HatRed Hat Integration Change Data CaptureNot specified in the recordNot stated
Red HatRed Hat Integration Service RegistryNot specified in the recordNot stated
Red HatRed Hat JBoss A-MQ 7Not specified in the recordNot stated
Red HatRed Hat JBoss Data Grid 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 6Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform 7Not specified in the recordNot stated
Red HatRed Hat JBoss Enterprise Application Platform Expansion PackNot specified in the recordNot stated
Red HatRed Hat JBoss Fuse 6Not specified in the recordNot stated
Red HatRed Hat JBoss Fuse 7Not specified in the recordNot stated
Red HatRed Hat JBoss Fuse Service Works 6Not specified in the recordNot stated
Red HatRed Hat JBoss Web Server 3Not specified in the recordNot stated
Red HatRed Hat JBoss Web Server 5Not specified in the recordNot stated
Red HatRed Hat OpenShift Application RuntimesNot specified in the recordNot stated

Version data comes from the organisation that assigned the CVE; 6 further products are omitted here. 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
LowNo special conditions are needed; the attack works reliably.
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
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

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

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

Official description

A flaw was found in codeplex-codehaus. A directory traversal attack (also known as path traversal) aims to access files and directories stored outside the intended folder. By manipulating files with "dot-dot-slash (../)" sequences and their variations or by using absolute file paths, it may be possible to access arbitrary files and directories stored on the file system, including application source code, configuration, and other critical system files.

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

The underlying weakness: Improper Limitation of a Pathname to a Restricted Directory

The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

How developers prevent this class of flaw

  • For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • Use an application firewall that can detect attacks against this weakness. It can be beneficial in cases in which the code cannot be fixed (because it is controlled by a third party), as an emergency prevention measure while more comprehensive software assurance measures are applied, or to provide defense in depth.

More Improper Limitation of a Pathname to a Restricted Directory vulnerabilities (CWE-22)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Third-party and government advisories

Recent Improper Limitation of a Pathname to a Restricted Directory vulnerabilities

Spotted an error? Tell us.