---
id: CVE-2023-4527
title: 'Glibc: stack read overflow in getaddrinfo in no-aaaa mode'
summary: >-
  A flaw was found in glibc. When the getaddrinfo function is called with the
  AF_UNSPEC address family and the system is configured with no-aaaa mode via
  /etc/resolv.conf, a DNS response via TCP larger than 2048 bytes can
  potentially discl…
severity: medium
cvss: 6.5
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:H'
cvssSource: cna
cwe:
  - CWE-121
vendor: Red Hat
product: glibc
affected:
  - glibc (all versions)
  - glibc (all versions)
  - glibc (all versions)
  - glibc (all versions)
  - compat-glibc
  - glibc
  - compat-glibc
  - glibc
ssvc:
  exploitation: none
  automatable: 'no'
  technicalImpact: partial
  timestamp: '2024-12-03T14:44:32.771215Z'
published: '2023-09-18'
updated: '2026-10-14'
sourceUpdated: '2026-10-14T21:32:18.501Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2023-4527'
references:
  - url: 'https://access.redhat.com/errata/RHSA-2023:5453'
    label: 'RHSA-2023:5453'
  - url: 'https://access.redhat.com/errata/RHSA-2023:5455'
    label: 'RHSA-2023:5455'
  - url: 'https://access.redhat.com/security/cve/CVE-2023-4527'
  - url: 'https://bugzilla.redhat.com/show_bug.cgi?id=2234712'
    label: RHBZ#2234712
tags:
  - cve.org
epss: 0.01669
epssPercentile: 0.76323
ingestedAt: '2026-10-15T04:46:37.149Z'
---

## Overview

A flaw was found in glibc. When the getaddrinfo function is called with the AF_UNSPEC address family and the system is configured with no-aaaa mode via /etc/resolv.conf, a DNS response via TCP larger than 2048 bytes can potentially disclose stack contents through the function returned address data, and may cause a crash.

## Affected

- `glibc (all versions)`
- `glibc (all versions)`
- `glibc (all versions)`
- `glibc (all versions)`
- `compat-glibc`
- `glibc`
- `compat-glibc`
- `glibc`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.

### Workarounds

Removing the no-aaaa diagnostic option from /etc/resolv.conf will mitigate this flaw.