Bug 2237798 (CVE-2023-4813)
Summary: | CVE-2023-4813 glibc: potential use-after-free in gaih_inet() | ||
---|---|---|---|
Product: | [Other] Security Response | Reporter: | Guilherme de Almeida Suckevicz <gsuckevi> |
Component: | vulnerability | Assignee: | Product Security <prodsec-ir-bot> |
Status: | NEW --- | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | unspecified | CC: | acrosby, adudiak, agarcial, aoconnor, asegurap, bdettelb, caswilli, codonell, dfreiber, dkuc, fjansen, fweimer, ganandan, ggastald, hkataria, jburrell, jmitchel, jsamir, jsherril, jtanner, kaycoth, kshier, luizcosta, mcermak, mcoufal, nweather, psegedy, rogbas, sbiarozk, security-response-team, sipoyare, skolosov, stcannon, sthirugn, tcarlin, tkasparek, vkrizan, vkumar, vmugicag, yguenane |
Target Milestone: | --- | Keywords: | Security |
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | glibc 2.36 | Doc Type: | If docs needed, set a value |
Doc Text: |
A flaw was found in glibc. In an uncommon situation, the gaih_inet function may use memory that has been freed, resulting in an application crash. This issue is only exploitable when the getaddrinfo function is called and the hosts database in /etc/nsswitch.conf is configured with SUCCESS=continue or SUCCESS=merge.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | Type: | --- | |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | 2238609 | ||
Bug Blocks: | 2234719 |
Description
Guilherme de Almeida Suckevicz
2023-09-07 01:14:24 UTC
Created glibc tracking bugs for this issue: Affects: fedora-all [bug 2238609] The immediate workaround for this is to drop the "SUCCESS=continue" or "SUCCESS=merge" in the hosts line in nsswitch.conf because those options are not supported on the hosts database. If they were working before, it was an accident because of this bug, it's not a feature. The fix for the bug results in this "feature" being dropped. This issue has been addressed in the following products: Red Hat Enterprise Linux 9 Via RHSA-2023:5453 https://access.redhat.com/errata/RHSA-2023:5453 This issue has been addressed in the following products: Red Hat Enterprise Linux 8 Via RHSA-2023:5455 https://access.redhat.com/errata/RHSA-2023:5455 This issue has been addressed in the following products: Red Hat Enterprise Linux 8.6 Extended Update Support Via RHSA-2023:7409 https://access.redhat.com/errata/RHSA-2023:7409 |