CVE Vulnerabilities

CVE-2022-42898

Integer Overflow or Wraparound

Published: Dec 25, 2022 | Modified: Apr 14, 2025
CVSS 3.x
8.8
HIGH
Source:
NVD
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
CVSS 2.x
RedHat/V2
RedHat/V3
8.8 IMPORTANT
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Ubuntu
MEDIUM
root.io logo minimus.io logo echo.ai logo

PAC parsing in MIT Kerberos 5 (aka krb5) before 1.19.4 and 1.20.x before 1.20.1 has integer overflows that may lead to remote code execution (in KDC, kadmind, or a GSS or Kerberos application server) on 32-bit platforms (which have a resultant heap-based buffer overflow), and cause a denial of service on other platforms. This occurs in krb5_pac_parse in lib/krb5/krb/pac.c. Heimdal before 7.7.1 has a similar bug.

Weakness

The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.

Affected Software

NameVendorStart VersionEnd Version
Kerberos_5Mit1.8 (including)1.19.4 (excluding)
Kerberos_5Mit1.20 (including)1.20 (including)
Kerberos_5Mit1.20-beta1 (including)1.20-beta1 (including)
Red Hat Enterprise Linux 6 Extended Lifecycle SupportRedHatkrb5-0:1.10.3-66.el6_10*
Red Hat Enterprise Linux 7RedHatkrb5-0:1.15.1-55.el7_9*
Red Hat Enterprise Linux 8RedHatkrb5-0:1.18.2-25.el8_8*
Red Hat Enterprise Linux 8RedHatkrb5-0:1.18.2-22.el8_7*
Red Hat Enterprise Linux 8.1 Update Services for SAP SolutionsRedHatkrb5-0:1.17-10.el8_1*
Red Hat Enterprise Linux 8.2 Advanced Update SupportRedHatkrb5-0:1.17-19.el8_2*
Red Hat Enterprise Linux 8.2 Telecommunications Update ServiceRedHatkrb5-0:1.17-19.el8_2*
Red Hat Enterprise Linux 8.2 Update Services for SAP SolutionsRedHatkrb5-0:1.17-19.el8_2*
Red Hat Enterprise Linux 8.4 Extended Update SupportRedHatkrb5-0:1.18.2-9.el8_4*
Red Hat Enterprise Linux 8.6 Extended Update SupportRedHatkrb5-0:1.18.2-15.el8_6*
Red Hat Enterprise Linux 9RedHatkrb5-0:1.19.1-24.el9_1*
Red Hat Enterprise Linux 9RedHatkrb5-0:1.19.1-24.el9_1*
Red Hat Enterprise Linux 9.0 Extended Update SupportRedHatkrb5-0:1.19.1-16.el9_0*
Red Hat Virtualization 4 for Red Hat Enterprise Linux 8RedHatredhat-virtualization-host-0:4.5.3-202212070734_8.6*
HeimdalUbuntubionic*
HeimdalUbuntudevel*
HeimdalUbuntuesm-apps/jammy*
HeimdalUbuntuesm-apps/noble*
HeimdalUbuntuesm-infra-legacy/trusty*
HeimdalUbuntuesm-infra/bionic*
HeimdalUbuntuesm-infra/focal*
HeimdalUbuntuesm-infra/xenial*
HeimdalUbuntufocal*
HeimdalUbuntujammy*
HeimdalUbuntukinetic*
HeimdalUbuntulunar*
HeimdalUbuntumantic*
HeimdalUbuntunoble*
HeimdalUbuntuoracular*
HeimdalUbuntuplucky*
HeimdalUbuntuquesting*
HeimdalUbuntutrusty*
HeimdalUbuntutrusty/esm*
HeimdalUbuntuupstream*
HeimdalUbuntuxenial*
Krb5Ubuntubionic*
Krb5Ubuntuesm-infra-legacy/trusty*
Krb5Ubuntuesm-infra/bionic*
Krb5Ubuntuesm-infra/focal*
Krb5Ubuntuesm-infra/xenial*
Krb5Ubuntufocal*
Krb5Ubuntujammy*
Krb5Ubuntukinetic*
Krb5Ubuntutrusty*
Krb5Ubuntutrusty/esm*
Krb5Ubuntuupstream*
Krb5Ubuntuxenial*
SambaUbuntubionic*
SambaUbuntuesm-infra-legacy/trusty*
SambaUbuntuesm-infra/bionic*
SambaUbuntuesm-infra/focal*
SambaUbuntuesm-infra/xenial*
SambaUbuntufocal*
SambaUbuntujammy*
SambaUbuntukinetic*
SambaUbuntutrusty*
SambaUbuntutrusty/esm*
SambaUbuntuupstream*
SambaUbuntuxenial*

Potential Mitigations

  • Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
  • If possible, choose a language or compiler that performs automatic bounds checking.
  • Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid [REF-1482].
  • Use libraries or frameworks that make it easier to handle numbers without unexpected consequences.
  • Examples include safe integer handling packages such as SafeInt (C++) or IntegerLib (C or C++). [REF-106]
  • Perform input validation on any numeric input by ensuring that it is within the expected range. Enforce that the input meets both the minimum and maximum requirements for the expected range.
  • Use unsigned integers where possible. This makes it easier to perform validation for integer overflows. When signed integers are required, ensure that the range check includes minimum values as well as maximum values.
  • Understand the programming language’s underlying representation and how it interacts with numeric calculation (CWE-681). Pay close attention to byte size discrepancies, precision, signed/unsigned distinctions, truncation, conversion and casting between types, “not-a-number” calculations, and how the language handles numbers that are too large or too small for its underlying representation. [REF-7]
  • Also be careful to account for 32-bit, 64-bit, and other potential differences that may affect the numeric representation.

References