Detections
Analytics

Fedora 37 : java-11-openjdk (2022-945d2996cd)

medium Nessus Plugin ID 210962

Synopsis

The remote Fedora host is missing one or more security updates.

Description

The remote Fedora 37 host has a package installed that is affected by multiple vulnerabilities as referenced in the FEDORA-2022-945d2996cd advisory.

 # New in release OpenJDK 11.0.17 (2022-10-18)

 * [Release announcement](https://bit.ly/openjdk11017)
 * [Full release notes](https://builds.shipilev.net/backports-monitor/release-notes-11.0.7.html)

 ## Security Fixes
 - JDK-8282252: Improve BigInteger/Decimal validation
 - JDK-8285662: Better permission resolution
 - JDK-8286077, CVE-2022-21618: Wider MultiByte conversions
 - JDK-8286511: Improve macro allocation
 - JDK-8286519: Better memory handling
 - JDK-8286526, CVE-2022-21619: Improve NTLM support
 - JDK-8286533, CVE-2022-21626: Key X509 usages
 - JDK-8286910, CVE-2022-21624: Improve JNDI lookups
 - JDK-8286918, CVE-2022-21628: Better HttpServer service
 - JDK-8287446: Enhance icon presentations
 - JDK-8288508: Enhance ECDSA usage
 - JDK-8289366, CVE-2022-39399: Improve HTTP/2 client usage
 - JDK-8289853: Update HarfBuzz to 4.4.1
 - JDK-8290334: Update FreeType to 2.12.1
 - JDK-8293429: [11u] minor update in attribute style

 ## Major Changes

 ### [JDK-8278067](https://bugs.openjdk.org/browse/JDK-8278067): Make HttpURLConnection Default Keep Alive Timeout Configurable Two system properties have been added which control the keep alive behavior of HttpURLConnection in the case where the server does not specify a keep alive time. Two properties are defined for controlling connections to servers and proxies separately. They are:

 * `http.keepAlive.time.server`
 * `http.keepAlive.time.proxy`

 respectively. More information about them can be found on the [Networking Properties page](https://docs.oracle.com/en/java/javase/17/docs/api/java.base/java/net/doc-files/net- properties.html).

 ### JDK-8286918: Better HttpServer service The HttpServer can be optionally configured with a maximum connection limit by setting the jdk.httpserver.maxConnections system property. A value of `0` or a negative integer is ignored and considered to represent no connection limit. In the case of a positive integer value, any newly accepted connections will be first checked against the current count of established connections and, if the configured limit has been reached, then the newly accepted connection will be closed immediately.

 ### [JDK-8281181](https://bugs.openjdk.org/browse/JDK-8281181): CPU Shares Ignored When Computing Active Processor Count Previous JDK releases used an incorrect interpretation of the Linux cgroups parameter cpu.shares. This might cause the JVM to use fewer CPUs than available, leading to an under utilization of CPU resources when the JVM is used inside a container.

 Starting from this JDK release, by default, the JVM no longer considers cpu.shares when deciding the number of threads to be used by the various thread pools. The `-XX:+UseContainerCpuShares` command-line option can be used to revert to the previous behaviour. This option is deprecated and may be removed in a future JDK release.

 ### [JDK-8269039](https://bugs.openjdk.org/browse/JDK-8269039): Disabled SHA-1 Signed JARs JARs signed with SHA-1 algorithms are now restricted by default and treated as if they were unsigned. This applies to the algorithms used to digest, sign, and optionally timestamp the JAR. It also applies to the signature and digest algorithms of the certificates in the certificate chain of the code signer and the Timestamp Authority, and any CRLs or OCSP responses that are used to verify if those certificates have been revoked. These restrictions also apply to signed JCE providers.

 To reduce the compatibility risk for JARs that have been previously timestamped, there is one exception to this policy:

 - Any JAR signed with SHA-1 algorithms and timestamped prior to January 01, 2019 will not be restricted.

 This exception may be removed in a future JDK release. To determine if your signed JARs are affected by this change, run:
 ~~~ $ jarsigner -verify -verbose -certs` ~~~ on the signed JAR, and look for instances of SHA1 or SHA-1 and disabled and a warning that the JAR will be treated as unsigned in the output.

 For example:
 ~~~ Signed by CN=Signer Digest algorithm: SHA-1 (disabled) Signature algorithm: SHA1withRSA (disabled), 2048-bit key

 WARNING: The jar will be treated as unsigned, because it is signed with a weak algorithm that is now disabled by the security property:

 jdk.jar.disabledAlgorithms=MD2, MD5, RSA keySize < 1024, DSA keySize < 1024, SHA1 denyAfter 2019-01-01 ~~~ JARs affected by these new restrictions should be replaced or re-signed with stronger algorithms.

 Users can, *at their own risk*, remove these restrictions by modifying the `java.security` configuration file (or override it by using the `java.security.properties` system property) and removing SHA1 usage SignedJAR & denyAfter 2019-01-01 from the `jdk.certpath.disabledAlgorithms` security property and SHA1 denyAfter 2019-01-01 from the `jdk.jar.disabledAlgorithms` security property.

 ### [JDK-8267880](https://bugs.openjdk.org/browse/JDK-8267880): Upgrade the default PKCS12 MAC algorithm The default MAC algorithm used in a PKCS #12 keystore has been updated. The new algorithm is based on SHA-256 and is stronger than the old one based on SHA-1. See the security properties starting with `keystore.pkcs12` in the `java.security` file for detailed information.

 The new SHA-256 based MAC algorithms were introduced in the 11.0.12 release. Keystores created using this newer, stronger, MAC algorithm cannot be opened in versions of OpenJDK 11 earlier than 11.0.12. A 'java.security.NoSuchAlgorithmException' exception will be thrown in such circumstances.

 For compatibility, use the `keystore.pkcs12.legacy` system property, which will revert the algorithms to use the older, weaker algorithms. There is no value defined for this property.

 ### [JDK-8261160](https://bugs.openjdk.org/browse/JDK-8261160): JDK Flight Recorder Event for Deserialization It is now possible to monitor deserialization of objects using JDK Flight Recorder (JFR). When JFR is enabled and the JFR configuration includes deserialization events, JFR will emit an event whenever the running program attempts to deserialize an object. The deserialization event is named `jdk.Deserialization`, and it is disabled by default. The deserialization event contains information that is used by the serialization filter mechanism; see the ObjectInputFilter API specification for details.

 Additionally, if a filter is enabled, the JFR event indicates whether the filter accepted or rejected deserialization of the object. For further information about how to use the JFR deserialization event, see the article [Monitoring Deserialization to Improve Application Security](https://inside.java/2021/03/02/monitoring- deserialization-activity-in-the-jdk/).

 For reference information about using and configuring JFR, see the [JFR Runtime Guide](https://docs.oracle.com/javacomponents/jmc-5-5/jfr-runtime-guide/preface_jfrrt.htm#JFRRT165) and [JFR Command Reference](https://docs.oracle.com/javacomponents/jmc-5-5/jfr-command-reference/command- line-options.htm#JFRCR-GUID-FE61CA60-E1DF-460E-A8E0-F4FF5D58A7A0) sections of the JDK Mission Control documentation.

 ### [JDK-8139348](https://bugs.openjdk.org/browse/JDK-8139348): Deprecate 3DES and RC4 in Kerberos The `des3-hmac-sha1` and `rc4-hmac` Kerberos encryption types (etypes) are now deprecated and disabled by default. Users can set `allow_weak_crypto = true` in the `krb5.conf` configuration file to re-enable them (along with other weak etypes including `des-cbc-crc` and `des-cbc-md5`) at their own risk. To disable a subset of the weak etypes, users can list preferred etypes explicitly in any of the `default_tkt_enctypes`, `default_tgs_enctypes`, or `permitted_enctypes` settings.


Tenable has extracted the preceding description block directly from the Fedora security advisory.

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

Solution

Update the affected 1:java-11-openjdk package.

See Also

https://bodhi.fedoraproject.org/updates/FEDORA-2022-945d2996cd

Plugin Details

Severity: Medium

ID: 210962

File Name: fedora_2022-945d2996cd.nasl

Version: 1.1

Type: local

Agent: unix

Published: 11/14/2024

Updated: 11/14/2024

Supported Sensors: Nessus Agent, continuous_assessment, Nessus

Risk Information

VPR

Risk Factor: Low

Score: 2.2

CVSS v2

Risk Factor: Medium

Base Score: 5

Temporal Score: 3.7

Vector: CVSS2#AV:N/AC:L/Au:N/C:N/I:P/A:N

CVSS Score Source: CVE-2022-21618

CVSS v3

Risk Factor: Medium

Base Score: 5.3

Temporal Score: 4.6

Vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Temporal Vector: CVSS:3.0/E:U/RL:O/RC:C

Vulnerability Information

CPE: p-cpe:/a:fedoraproject:fedora:java-11-openjdk, cpe:/o:fedoraproject:fedora:37

Required KB Items: Host/local_checks_enabled, Host/RedHat/release, Host/RedHat/rpm-list

Exploit Ease: No known exploits are available

Patch Publication Date: 10/26/2022

Vulnerability Publication Date: 10/17/2022

Reference Information

CVE: CVE-2022-21618, CVE-2022-21619, CVE-2022-21624, CVE-2022-21626, CVE-2022-21628, CVE-2022-39399