Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1973402 [details]
twistlock.png

User noticed Twistlock logs claim nodejs 18 is affected by issue
as shown in the attached file.

  Checking what should be related patch
https://github.com/nodejs/node/pull/47335/commits/84ad3bc7b8ddbe57a718ea1467a21f48a3505619
it does not apply to nodejs 18, and in comment
https://github.com/nodejs/node/pull/47335#issuecomment-1593912485
it appears to make it clear the issue does not apply to nodejs 18,
as it is a nodejs 20 feature.

  Can you please confirm the log is incorrect?

  Actual software in use is

UBI_BASE_IMAGE="registry.access.redhat.com/ubi8/nodejs-18-minimal"
ubi image nodejs-18-minimal

Michael, can you take a look to confirm node 18 is not affected?

Taking a look this, the code in question never made it into any official release. The permissions model was only release in 20.x and the deny api was removed before that release. Therefore it does not affect 18.x since it does not include the permission model. Note it also does not affect 20.x since it was not part of the initial release of the permission model as well.

Thanks! Closing this bug then.