Improper Handling of Exceptional Conditions Affecting osbuild-composer-dnf-json package, versions *


Severity

Recommended
0.0
low
0
10

Based on Red Hat Enterprise Linux security rating.

Threat Intelligence

EPSS
0.04% (11th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications
  • Snyk IDSNYK-RHEL9-OSBUILDCOMPOSERDNFJSON-8342642
  • published5 Nov 2024
  • disclosed4 Nov 2024

Introduced: 4 Nov 2024

CVE-2024-51744  (opens in a new tab)
CWE-755  (opens in a new tab)

How to fix?

There is no fixed version for RHEL:9 osbuild-composer-dnf-json.

NVD Description

Note: Versions mentioned in the description apply only to the upstream osbuild-composer-dnf-json package and not the osbuild-composer-dnf-json package as distributed by RHEL. See How to fix? for RHEL:9 relevant fixed versions and status.

golang-jwt is a Go implementation of JSON Web Tokens. Unclear documentation of the error behavior in ParseWithClaims can lead to situation where users are potentially not checking errors in the way they should be. Especially, if a token is both expired and invalid, the errors returned by ParseWithClaims return both error codes. If users only check for the jwt.ErrTokenExpired using error.Is, they will ignore the embedded jwt.ErrTokenSignatureInvalid and thus potentially accept invalid tokens. A fix has been back-ported with the error handling logic from the v5 branch to the v4 branch. In this logic, the ParseWithClaims function will immediately return in "dangerous" situations (e.g., an invalid signature), limiting the combined errors only to situations where the signature is valid, but further validation failed (e.g., if the signature is valid, but is expired AND has the wrong audience). This fix is part of the 4.5.1 release. We are aware that this changes the behaviour of an established function and is not 100 % backwards compatible, so updating to 4.5.1 might break your code. In case you cannot update to 4.5.0, please make sure that you are properly checking for all errors ("dangerous" ones first), so that you are not running in the case detailed above.

CVSS Scores

version 3.1