CVSS2
Attack Vector
LOCAL
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:L/AC:M/Au:N/C:P/I:P/A:P
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
AI Score
Confidence
High
EPSS
Percentile
83.5%
The remote Red Hat Enterprise Linux CoreOS 4 host has packages installed that are affected by multiple vulnerabilities as referenced in the RHSA-2023:4093 advisory.
An authentication bypass vulnerability was discovered in kube-apiserver. This issue could allow a remote, authenticated attacker who has been given permissions update, patch the pods/ephemeralcontainers subresource beyond what the default is. They would then need to create a new pod or patch one that they already have access to. This might allow evasion of SCC admission restrictions, thereby gaining control of a privileged pod. (CVE-2023-1260)
HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs, potentially leading to a denial of service. Certain unusual patterns of input data can cause the common function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.
With fix, header parsing now correctly allocates only the memory required to hold parsed headers.
(CVE-2023-24534)
Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed, leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3.
ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage collector. The combination of these factors can permit an attacker to cause an program that parses multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service.
This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix, ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with the environment variable GODEBUG=multipartmaxheaders=. (CVE-2023-24536)
Calling any of the Parse functions on Go source code which contains //line directives with very large line numbers can cause an infinite loop due to integer overflow. (CVE-2023-24537)
Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template action within a Javascript template literal, the contents of the action can be used to terminate the literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather complex, and themselves can do string interpolation, the decision was made to simply disallow Go template actions from being used inside of them (e.g. var a = {{.}}), since there is no obviously safe way to allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template.Parse returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is currently unexported, but will be exported in the release of Go 1.21. Users who rely on the previous behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will now be escaped. This should be used with caution. (CVE-2023-24538)
Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates containing multiple actions separated by a ‘/’ character can result in unexpectedly closing the CSS context and allowing for injection of unexpected HTML, if executed with untrusted input. (CVE-2023-24539)
runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a CVE-2019-19921 regression. (CVE-2023-27561)
Templates containing actions in unquoted HTML attributes (e.g. attr={{.}}) executed with empty input can result in output with unexpected results when parsed due to HTML normalization rules. This may allow injection of arbitrary attributes into tags. (CVE-2023-29400)
A compliance problem was found in the Red Hat OpenShift Container Platform. Red Hat discovered that, when FIPS mode was enabled, not all of the cryptographic modules in use were FIPS-validated. (CVE-2023-3089)
Note that Nessus has not tested for these issues but has instead relied only on the application’s self-reported version number.
#%NASL_MIN_LEVEL 80900
##
# (C) Tenable, Inc.
#
# The descriptive text and package checks in this plugin were
# extracted from Red Hat Security Advisory RHSA-2023:4093. The text
# itself is copyright (C) Red Hat, Inc.
##
include('compat.inc');
if (description)
{
script_id(189410);
script_version("1.0");
script_set_attribute(attribute:"plugin_modification_date", value:"2024/01/24");
script_cve_id(
"CVE-2023-1260",
"CVE-2023-3089",
"CVE-2023-24534",
"CVE-2023-24536",
"CVE-2023-24537",
"CVE-2023-24538",
"CVE-2023-24539",
"CVE-2023-27561",
"CVE-2023-29400"
);
script_xref(name:"RHSA", value:"2023:4093");
script_name(english:"RHCOS 4 : OpenShift Container Platform 4.13.5 (RHSA-2023:4093)");
script_set_attribute(attribute:"synopsis", value:
"The remote Red Hat CoreOS host is missing one or more security updates for OpenShift Container Platform 4.13.5.");
script_set_attribute(attribute:"description", value:
"The remote Red Hat Enterprise Linux CoreOS 4 host has packages installed that are affected by multiple vulnerabilities
as referenced in the RHSA-2023:4093 advisory.
- An authentication bypass vulnerability was discovered in kube-apiserver. This issue could allow a remote,
authenticated attacker who has been given permissions update, patch the pods/ephemeralcontainers
subresource beyond what the default is. They would then need to create a new pod or patch one that they
already have access to. This might allow evasion of SCC admission restrictions, thereby gaining control of
a privileged pod. (CVE-2023-1260)
- HTTP and MIME header parsing can allocate large amounts of memory, even when parsing small inputs,
potentially leading to a denial of service. Certain unusual patterns of input data can cause the common
function used to parse HTTP and MIME headers to allocate substantially more memory than required to hold
the parsed headers. An attacker can exploit this behavior to cause an HTTP server to allocate large
amounts of memory from a small request, potentially leading to memory exhaustion and a denial of service.
With fix, header parsing now correctly allocates only the memory required to hold parsed headers.
(CVE-2023-24534)
- Multipart form parsing can consume large amounts of CPU and memory when processing form inputs containing
very large numbers of parts. This stems from several causes: 1. mime/multipart.Reader.ReadForm limits the
total memory a parsed multipart form can consume. ReadForm can undercount the amount of memory consumed,
leading it to accept larger inputs than intended. 2. Limiting total memory does not account for increased
pressure on the garbage collector from large numbers of small allocations in forms with many parts. 3.
ReadForm can allocate a large number of short-lived buffers, further increasing pressure on the garbage
collector. The combination of these factors can permit an attacker to cause an program that parses
multipart forms to consume large amounts of CPU and memory, potentially resulting in a denial of service.
This affects programs that use mime/multipart.Reader.ReadForm, as well as form parsing in the net/http
package with the Request methods FormFile, FormValue, ParseMultipartForm, and PostFormValue. With fix,
ReadForm now does a better job of estimating the memory consumption of parsed forms, and performs many
fewer short-lived allocations. In addition, the fixed mime/multipart.Reader imposes the following limits
on the size of parsed forms: 1. Forms parsed with ReadForm may contain no more than 1000 parts. This limit
may be adjusted with the environment variable GODEBUG=multipartmaxparts=. 2. Form parts parsed with
NextPart and NextRawPart may contain no more than 10,000 header fields. In addition, forms parsed with
ReadForm may contain no more than 10,000 header fields across all parts. This limit may be adjusted with
the environment variable GODEBUG=multipartmaxheaders=. (CVE-2023-24536)
- Calling any of the Parse functions on Go source code which contains //line directives with very large line
numbers can cause an infinite loop due to integer overflow. (CVE-2023-24537)
- Templates do not properly consider backticks (`) as Javascript string delimiters, and do not escape them
as expected. Backticks are used, since ES6, for JS template literals. If a template contains a Go template
action within a Javascript template literal, the contents of the action can be used to terminate the
literal, injecting arbitrary Javascript code into the Go template. As ES6 template literals are rather
complex, and themselves can do string interpolation, the decision was made to simply disallow Go template
actions from being used inside of them (e.g. var a = {{.}}), since there is no obviously safe way to
allow this behavior. This takes the same approach as github.com/google/safehtml. With fix, Template.Parse
returns an Error when it encounters templates like this, with an ErrorCode of value 12. This ErrorCode is
currently unexported, but will be exported in the release of Go 1.21. Users who rely on the previous
behavior can re-enable it using the GODEBUG flag jstmpllitinterp=1, with the caveat that backticks will
now be escaped. This should be used with caution. (CVE-2023-24538)
- Angle brackets (<>) are not considered dangerous characters when inserted into CSS contexts. Templates
containing multiple actions separated by a '/' character can result in unexpectedly closing the CSS
context and allowing for injection of unexpected HTML, if executed with untrusted input. (CVE-2023-24539)
- runc through 1.1.4 has Incorrect Access Control leading to Escalation of Privileges, related to
libcontainer/rootfs_linux.go. To exploit this, an attacker must be able to spawn two containers with
custom volume-mount configurations, and be able to run custom images. NOTE: this issue exists because of a
CVE-2019-19921 regression. (CVE-2023-27561)
- Templates containing actions in unquoted HTML attributes (e.g. attr={{.}}) executed with empty input can
result in output with unexpected results when parsed due to HTML normalization rules. This may allow
injection of arbitrary attributes into tags. (CVE-2023-29400)
- A compliance problem was found in the Red Hat OpenShift Container Platform. Red Hat discovered that, when
FIPS mode was enabled, not all of the cryptographic modules in use were FIPS-validated. (CVE-2023-3089)
Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version
number.");
script_set_attribute(attribute:"see_also", value:"https://access.redhat.com/security/cve/CVE-2023-1260");
script_set_attribute(attribute:"see_also", value:"https://access.redhat.com/security/cve/CVE-2023-3089");
script_set_attribute(attribute:"see_also", value:"https://access.redhat.com/security/cve/CVE-2023-24534");
script_set_attribute(attribute:"see_also", value:"https://access.redhat.com/security/cve/CVE-2023-24536");
script_set_attribute(attribute:"see_also", value:"https://access.redhat.com/security/cve/CVE-2023-24537");
script_set_attribute(attribute:"see_also", value:"https://access.redhat.com/security/cve/CVE-2023-24538");
script_set_attribute(attribute:"see_also", value:"https://access.redhat.com/security/cve/CVE-2023-24539");
script_set_attribute(attribute:"see_also", value:"https://access.redhat.com/security/cve/CVE-2023-27561");
script_set_attribute(attribute:"see_also", value:"https://access.redhat.com/security/cve/CVE-2023-29400");
script_set_attribute(attribute:"see_also", value:"https://access.redhat.com/errata/RHSA-2023:4093");
script_set_attribute(attribute:"see_also", value:"https://bugzilla.redhat.com/2175721");
script_set_attribute(attribute:"solution", value:
"Update the RHCOS OpenShift Container Platform 4.13.5 package based on the guidance in RHSA-2023:4093.");
script_set_cvss_base_vector("CVSS2#AV:N/AC:L/Au:N/C:C/I:C/A:C");
script_set_cvss_temporal_vector("CVSS2#E:POC/RL:OF/RC:C");
script_set_cvss3_base_vector("CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H");
script_set_cvss3_temporal_vector("CVSS:3.0/E:P/RL:O/RC:C");
script_set_attribute(attribute:"cvss_score_source", value:"CVE-2023-24538");
script_set_attribute(attribute:"exploitability_ease", value:"Exploits are available");
script_set_attribute(attribute:"exploit_available", value:"true");
script_cwe_id(41, 94, 166, 176, 288, 400, 693, 835);
script_set_attribute(attribute:"vendor_severity", value:"Important");
script_set_attribute(attribute:"vuln_publication_date", value:"2023/03/03");
script_set_attribute(attribute:"patch_publication_date", value:"2023/07/20");
script_set_attribute(attribute:"plugin_publication_date", value:"2024/01/24");
script_set_attribute(attribute:"plugin_type", value:"local");
script_set_attribute(attribute:"cpe", value:"cpe:/o:redhat:enterprise_linux:8:coreos");
script_set_attribute(attribute:"cpe", value:"cpe:/o:redhat:enterprise_linux:9:coreos");
script_set_attribute(attribute:"cpe", value:"p-cpe:/a:redhat:enterprise_linux:openshift-clients");
script_set_attribute(attribute:"cpe", value:"p-cpe:/a:redhat:enterprise_linux:openshift-clients-redistributable");
script_set_attribute(attribute:"cpe", value:"p-cpe:/a:redhat:enterprise_linux:openshift-hyperkube");
script_set_attribute(attribute:"generated_plugin", value:"current");
script_end_attributes();
script_category(ACT_GATHER_INFO);
script_family(english:"Red Hat Local Security Checks");
script_copyright(english:"This script is Copyright (C) 2024 and is owned by Tenable, Inc. or an Affiliate thereof.");
script_dependencies("ssh_get_info.nasl");
script_require_keys("Host/local_checks_enabled", "Host/RedHat/release", "Host/RedHat/rpm-list", "Host/cpu");
exit(0);
}
include('rpm.inc');
include('rhel.inc');
if (!get_kb_item('Host/local_checks_enabled')) audit(AUDIT_LOCAL_CHECKS_NOT_ENABLED);
var os_release = get_kb_item('Host/RedHat/release');
if (isnull(os_release) || 'Red Hat' >!< os_release) audit(AUDIT_OS_NOT, 'Red Hat');
var os_ver = pregmatch(pattern: "Red Hat Enterprise Linux.*release ([0-9]+(\.[0-9]+)?)", string:os_release);
if (isnull(os_ver)) audit(AUDIT_UNKNOWN_APP_VER, 'Red Hat CoreOS');
os_ver = os_ver[1];
if (!rhel_check_release(operator: 'eq', os_version: os_ver, rhel_version: '4.13')) audit(AUDIT_OS_NOT, 'Red Hat CoreOS 4.13', 'Red Hat CoreOS ' + os_ver);
if (!get_kb_item('Host/RedHat/rpm-list')) audit(AUDIT_PACKAGE_LIST_MISSING);
var cpu = get_kb_item('Host/cpu');
if (isnull(cpu)) audit(AUDIT_UNKNOWN_ARCH);
if ('x86_64' >!< cpu && cpu !~ "^i[3-6]86$" && 's390' >!< cpu && 'aarch64' >!< cpu && 'ppc' >!< cpu) audit(AUDIT_LOCAL_CHECKS_NOT_IMPLEMENTED, 'Red Hat CoreOS', cpu);
var pkgs = [
{'reference':'openshift-clients-4.13.0-202306230038.p0.ge4c9a6a.assembly.stream.el8', 'release':'4', 'el_string':'el8', 'rpm_spec_vers_cmp':TRUE, 'exists_check':'openshift-hyperkube'},
{'reference':'openshift-clients-4.13.0-202306230038.p0.ge4c9a6a.assembly.stream.el9', 'release':'4', 'el_string':'el9', 'rpm_spec_vers_cmp':TRUE, 'exists_check':'openshift-hyperkube'},
{'reference':'openshift-clients-redistributable-4.13.0-202306230038.p0.ge4c9a6a.assembly.stream.el8', 'cpu':'x86_64', 'release':'4', 'el_string':'el8', 'rpm_spec_vers_cmp':TRUE, 'exists_check':'openshift-hyperkube'},
{'reference':'openshift-clients-redistributable-4.13.0-202306230038.p0.ge4c9a6a.assembly.stream.el9', 'cpu':'x86_64', 'release':'4', 'el_string':'el9', 'rpm_spec_vers_cmp':TRUE, 'exists_check':'openshift-hyperkube'},
{'reference':'openshift-hyperkube-4.13.0-202307132344.p0.gf245ced.assembly.stream.el8', 'release':'4', 'el_string':'el8', 'rpm_spec_vers_cmp':TRUE, 'exists_check':'openshift-hyperkube'},
{'reference':'openshift-hyperkube-4.13.0-202307132344.p0.gf245ced.assembly.stream.el9', 'release':'4', 'el_string':'el9', 'rpm_spec_vers_cmp':TRUE, 'exists_check':'openshift-hyperkube'}
];
var flag = 0;
foreach var package_array ( pkgs ) {
var reference = NULL;
var _release = NULL;
var _cpu = NULL;
var el_string = NULL;
var rpm_spec_vers_cmp = NULL;
var epoch = NULL;
if (!empty_or_null(package_array['reference'])) reference = package_array['reference'];
if (!empty_or_null(package_array['release'])) _release = 'RHCOS' + package_array['release'];
if (!empty_or_null(package_array['cpu'])) _cpu = package_array['cpu'];
if (!empty_or_null(package_array['el_string'])) el_string = package_array['el_string'];
if (!empty_or_null(package_array['rpm_spec_vers_cmp'])) rpm_spec_vers_cmp = package_array['rpm_spec_vers_cmp'];
if (!empty_or_null(package_array['epoch'])) epoch = package_array['epoch'];
if (reference &&
_release &&
(!exists_check || rpm_exists(release:_release, rpm:exists_check)) &&
rpm_check(release:_release, sp:sp, cpu:_cpu, reference:reference, epoch:epoch, el_string:el_string, rpm_spec_vers_cmp:rpm_spec_vers_cmp)) flag++;
}
if (flag)
{
security_report_v4(
port : 0,
severity : SECURITY_HOLE,
extra : rpm_report_get()
);
exit(0);
}
else
{
var tested = pkg_tests_get();
if (tested) audit(AUDIT_PACKAGE_NOT_AFFECTED, tested);
else audit(AUDIT_PACKAGE_NOT_INSTALLED, 'openshift-clients / openshift-clients-redistributable / etc');
}
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-1260
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24534
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24536
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24537
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24538
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24539
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-27561
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-29400
cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-3089
access.redhat.com/errata/RHSA-2023:4093
access.redhat.com/security/cve/CVE-2023-1260
access.redhat.com/security/cve/CVE-2023-24534
access.redhat.com/security/cve/CVE-2023-24536
access.redhat.com/security/cve/CVE-2023-24537
access.redhat.com/security/cve/CVE-2023-24538
access.redhat.com/security/cve/CVE-2023-24539
access.redhat.com/security/cve/CVE-2023-27561
access.redhat.com/security/cve/CVE-2023-29400
access.redhat.com/security/cve/CVE-2023-3089
bugzilla.redhat.com/2175721
CVSS2
Attack Vector
LOCAL
Attack Complexity
MEDIUM
Authentication
NONE
Confidentiality Impact
PARTIAL
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:L/AC:M/Au:N/C:P/I:P/A:P
CVSS3
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
AI Score
Confidence
High
EPSS
Percentile
83.5%