BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2023
CVE-2023-32731High confidence

Information leak in gRPC

Google · gRPC

7.4HighCVSS 3.1
Recommended action
Within 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • The selected CVSS metric records a network-reachable, unauthenticated path with no user interaction.
  • EPSS is 0.50% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs Google gRPC and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Distribution package intelligence

Release-specific package status

Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

5 package states
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Debian trixietrixie · sourcegrpcNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian bookwormbookworm · sourcegrpcNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian forkyforky · sourcegrpcNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Debian sidsid · sourcegrpcNot affectedDebian marks this release not affected (fixed-version marker 0).Not published in this feedDebian Security Tracker ↗Source updated 5 Oct 2026
Ubuntu 24.04 LTSnoble · standard archivegrpcUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Open-source package ranges12 source-attributed ranges

These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.

Ecosystem and packageAffected rangeFirst fixed versionEvidence
Mavenio.grpc:grpc-protobufECOSYSTEM: introduced 1.53.0; fixed 1.53.11.53.1OSV record ↗aggregator derived · 10 Sep 2026
Mavenio.grpc:grpc-protobufECOSYSTEM: introduced 1.54.0; fixed 1.54.21.54.2OSV record ↗aggregator derived · 10 Sep 2026
PyPIgrpcioECOSYSTEM: introduced 1.53.0; fixed 1.53.11.53.1OSV record ↗aggregator derived · 10 Sep 2026
PyPIgrpcioECOSYSTEM: introduced 1.54.0; fixed 1.54.21.54.2OSV record ↗aggregator derived · 10 Sep 2026
RubyGemsgrpcECOSYSTEM: introduced 1.53.0; fixed 1.53.11.53.1OSV record ↗aggregator derived · 10 Sep 2026
RubyGemsgrpcECOSYSTEM: introduced 1.54.0; fixed 1.54.21.54.2OSV record ↗aggregator derived · 10 Sep 2026
mavenio.grpc:grpc-protobuf>= 1.53.0, < 1.53.11.53.1GitHub advisory ↗github reviewed aggregator · 13 Aug 2025
mavenio.grpc:grpc-protobuf>= 1.54.0, < 1.54.21.54.2GitHub advisory ↗github reviewed aggregator · 13 Aug 2025
pipgrpcio>= 1.53.0, < 1.53.11.53.1GitHub advisory ↗github reviewed aggregator · 13 Aug 2025
pipgrpcio>= 1.54.0, < 1.54.21.54.2GitHub advisory ↗github reviewed aggregator · 13 Aug 2025
rubygemsgrpc>= 1.53.0, < 1.53.11.53.1GitHub advisory ↗github reviewed aggregator · 13 Aug 2025
rubygemsgrpc>= 1.54.0, < 1.54.21.54.2GitHub advisory ↗github reviewed aggregator · 13 Aug 2025
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2023-32731 · CSAF 2.0 · revision 17 · interimSUSE Product Security TeamCVE-2023-32731
173 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • grpc as component of SUSE Enterprise Storage 6
  • grpc-devel as component of SUSE Enterprise Storage 6
  • grpc-source as component of SUSE Enterprise Storage 6
  • libgrpc++1 as component of SUSE Enterprise Storage 6
  • libgrpc8 as component of SUSE Enterprise Storage 6
  • python2-grpcio as component of SUSE Enterprise Storage 6
  • python3-grpcio as component of SUSE Enterprise Storage 6
  • grpc as component of SUSE Enterprise Storage 7.1
  • python3-grpcio as component of SUSE Enterprise Storage 7.1
  • grpc as component of SUSE Enterprise Storage 7
  • libgrpc8 as component of SUSE Enterprise Storage 7
  • python3-grpcio as component of SUSE Enterprise Storage 7
Summary
When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing the rest of the HPACK frame. This caused any HPACK table mutations to also be skipped, resulting in a desynchronization of HPACK tables between sender and receiver. If leveraged, say, between a proxy and a backend, this could lead to requests from the proxy being interpreted as containing headers from different proxy clients - leading to an information leak that can be used for privilege escalation or data exfiltration. We recommend upgrading beyond the commit contained in https://github.com/grpc/grpc/pull/33005 https://github.com/grpc/grpc/pull/33005
Remediation
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2023-2030

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionWithin 7 days

High technical severity; prioritise exposed affected systems while verifying vendor guidance.

Patch available
01

What, why and how

When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing the rest of the HPACK frame. This caused any HPACK table mutations to also be skipped, resulting in a desynchronization of HPACK tables between sender and receiver. If leveraged, say, between a proxy and a backend, this could lead to requests from the proxy being interpreted as containing headers from different proxy clients - leading to an information leak that can be used for privilege escalation or data exfiltration. We recommend upgrading beyond the commit contained in  https://github.com/grpc/grpc/pull/33005 https://github.com/grpc/grpc/pull/33005

What

When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing the rest of the HPACK frame. This caused any HPACK table mutations to also be skipped, resulting in a desynchronization of HPACK tables between sender and receiver. If leveraged, say, between a proxy and a backend, this could lead to requests from the proxy being interpreted as containing headers from different proxy clients - leading to an information leak that can be used for privilege escalation or data exfiltration. We recommend upgrading beyond the commit contained in  https://github.com/grpc/grpc/pull/33005 https://github.com/grpc/grpc/pull/33005

Why

A feature, API, or function does not perform according to its specification.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may gain additional privileges.

What

When gRPC HTTP2 stack raised a header size exceeded error, it skipped parsing the rest of the HPACK frame. This caused any HPACK table mutations to also be skipped, resulting in a desynchronization of HPACK tables between sender and receiver. If leveraged, say, between a proxy and a backend, this could lead to requests from the proxy being interpreted as containing headers from different proxy clients - leading to an information leak that can be used for privilege escalation or data exfiltration. We recommend upgrading beyond the commit contained in  https://github.com/grpc/grpc/pull/33005 https://github.com/grpc/grpc/pull/33005

Why

A feature, API, or function does not perform according to its specification.

How

An attacker operating through a network path may attempt exploitation without authentication or user interaction. If successful, the issue may gain additional privileges.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Expected Behavior Violation → gain additional privileges
Attack surface
Network
Privileges required
None: unauthenticated exploitation is possible
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Unchanged: impact remains within the vulnerable component's security authority
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-440 ↗

CWE-440: Expected Behavior Violation. A feature, API, or function does not perform according to its specification.

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:H

Common Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.PRNonePrivileges required: The attacker does not need an account or existing privileges.UINoneUser interaction: No action by another user is required.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.INoneIntegrity impact: No direct loss is represented by this metric.AHighAvailability impact: A successful attack can cause a major loss.
Post-exploitation / living off the land
No specific living-off-the-land technique is confirmed in the structured sources. Monitor normal administration tools for activity inconsistent with the affected service's baseline.
NetworkUnauthenticatedPrivilege escalationCWE-440
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

Cyber Security Agency of Singapore · English · CSA-SB-20230614Security Bulletin 14 Jun 2023

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 14 Jun 2023, published on 14 June 2023. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1137Multiples vulnérabilités dans les produits IBM

VERecord?id=CVE-2022-3171 Référence CVE CVE-2022-3509 https://www.cve.org/CVERecord?id=CVE-2022-3509 Référence CVE CVE-2022-3510 https://www.cve.org/CVERecord?id=CVE-2022-3510 Référence CVE CVE-2022-37434 https://www.cve.org/CVERecord?id=CVE-2022-37434 Référence CVE CVE-2023-1370 https://www.cve.org/CVERecord?id=CVE-2023-1370 Référence CVE CVE-2023-22049 https://www.cve.org/CVERecord?id=CVE-2023-22049 Référence CVE CVE-2023-22067 https://www.cve.org/CVERecord?id=CVE-2023-22067 Référence CVE CVE-2023-22081 https://www.cve.org/CVERecord?id=CVE-2023-22081 Référence CVE CVE-2023-29258 https://www.cve.org/CVERecord?id=CVE-2023-29258 Référence CVE CVE-2023-32731 https://www.cve.org/CVERecord?id=CVE-2023-32731 Référence CVE CVE-2023-33850 https://www.cve.org/CVERecord?id=CVE-2023-33850 Référence CVE CVE-2023-34462 https://www.cve.org/CVERecord?id=CVE-2023-34462 Référence CVE CVE-2023-38003 https://www.cve.org/CVERecord?id=CVE-2023-38003 Référence CVE CVE-2023-38264 https://www.cve.org/CVERecord?id=CVE-2023-38264 Référence CVE CVE-2023-38727 https://www.cve.org/CVERecord?id=CVE-2023-38727 Référence CVE CVE-2023-40687 https://www.cve.org/CVERecord?id=CVE-2023-40687 Référence CVE CVE-2023-40692 https://www.cve.org/CVERecord?id=CVE-2023-40692 Référence CVE CVE-2023-43020 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2025-AVI-1051Multiples vulnérabilités dans les produits IBM

De multiples vulnérabilités ont été découvertes dans les produits IBM. Certaines d'entre elles permettent à un attaquant de provoquer une exécution de code arbitraire à distance, une élévation de privilèges et un déni de service à distance.

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0939Multiples vulnérabilités dans les produits IBM

CVERecord?id=CVE-2020-14155 Référence CVE CVE-2022-3171 https://www.cve.org/CVERecord?id=CVE-2022-3171 Référence CVE CVE-2022-3509 https://www.cve.org/CVERecord?id=CVE-2022-3509 Référence CVE CVE-2022-3510 https://www.cve.org/CVERecord?id=CVE-2022-3510 Référence CVE CVE-2022-37434 https://www.cve.org/CVERecord?id=CVE-2022-37434 Référence CVE CVE-2023-1370 https://www.cve.org/CVERecord?id=CVE-2023-1370 Référence CVE CVE-2023-27859 https://www.cve.org/CVERecord?id=CVE-2023-27859 Référence CVE CVE-2023-29258 https://www.cve.org/CVERecord?id=CVE-2023-29258 Référence CVE CVE-2023-29267 https://www.cve.org/CVERecord?id=CVE-2023-29267 Référence CVE CVE-2023-32731 https://www.cve.org/CVERecord?id=CVE-2023-32731 Référence CVE CVE-2023-33850 https://www.cve.org/CVERecord?id=CVE-2023-33850 Référence CVE CVE-2023-34462 https://www.cve.org/CVERecord?id=CVE-2023-34462 Référence CVE CVE-2023-38003 https://www.cve.org/CVERecord?id=CVE-2023-38003 Référence CVE CVE-2023-38719 https://www.cve.org/CVERecord?id=CVE-2023-38719 Référence CVE CVE-2023-38727 https://www.cve.org/CVERecord?id=CVE-2023-38727 Référence CVE CVE-2023-38729 https://www.cve.org/CVERecord?id=CVE-2023-38729 Référence CVE CVE-2023-38740 https://www.cve.org/CVERecord?id=CVE-2023-38740 Référence CVE CVE-2023-40372 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0297Multiples vulnérabilités dans Juniper

ecord?id=CVE-2023-23914 Référence CVE CVE-2023-23915 https://www.cve.org/CVERecord?id=CVE-2023-23915 Référence CVE CVE-2023-23931 https://www.cve.org/CVERecord?id=CVE-2023-23931 Référence CVE CVE-2023-2603 https://www.cve.org/CVERecord?id=CVE-2023-2603 Référence CVE CVE-2023-2650 https://www.cve.org/CVERecord?id=CVE-2023-2650 Référence CVE CVE-2023-27043 https://www.cve.org/CVERecord?id=CVE-2023-27043 Référence CVE CVE-2023-28366 https://www.cve.org/CVERecord?id=CVE-2023-28366 Référence CVE CVE-2023-29491 https://www.cve.org/CVERecord?id=CVE-2023-29491 Référence CVE CVE-2023-32681 https://www.cve.org/CVERecord?id=CVE-2023-32681 Référence CVE CVE-2023-32731 https://www.cve.org/CVERecord?id=CVE-2023-32731 Référence CVE CVE-2023-32732 https://www.cve.org/CVERecord?id=CVE-2023-32732 Référence CVE CVE-2023-3446 https://www.cve.org/CVERecord?id=CVE-2023-3446 Référence CVE CVE-2023-3592 https://www.cve.org/CVERecord?id=CVE-2023-3592 Référence CVE CVE-2023-36054 https://www.cve.org/CVERecord?id=CVE-2023-36054 Référence CVE CVE-2023-38408 https://www.cve.org/CVERecord?id=CVE-2023-38408 Référence CVE CVE-2023-38545 https://www.cve.org/CVERecord?id=CVE-2023-38545 Référence CVE CVE-2023-38546 https://www.cve.org/CVERecord?id=CVE-2023-38546 Référence CVE CVE-2023-3978 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2024-AVI-0145Multiples vulnérabilités dans les produits IBM

ord?id=CVE-2023-29409 Référence CVE CVE-2023-2976 https://www.cve.org/CVERecord?id=CVE-2023-2976 Référence CVE CVE-2023-30987 https://www.cve.org/CVERecord?id=CVE-2023-30987 Référence CVE CVE-2023-30991 https://www.cve.org/CVERecord?id=CVE-2023-30991 Référence CVE CVE-2023-32002 https://www.cve.org/CVERecord?id=CVE-2023-32002 Référence CVE CVE-2023-32006 https://www.cve.org/CVERecord?id=CVE-2023-32006 Référence CVE CVE-2023-32360 https://www.cve.org/CVERecord?id=CVE-2023-32360 Référence CVE CVE-2023-32559 https://www.cve.org/CVERecord?id=CVE-2023-32559 Référence CVE CVE-2023-32681 https://www.cve.org/CVERecord?id=CVE-2023-32681 Référence CVE CVE-2023-32731 https://www.cve.org/CVERecord?id=CVE-2023-32731 Référence CVE CVE-2023-33850 https://www.cve.org/CVERecord?id=CVE-2023-33850 Référence CVE CVE-2023-34053 https://www.cve.org/CVERecord?id=CVE-2023-34053 Référence CVE CVE-2023-34054 https://www.cve.org/CVERecord?id=CVE-2023-34054 Référence CVE CVE-2023-34055 https://www.cve.org/CVERecord?id=CVE-2023-34055 Référence CVE CVE-2023-34062 https://www.cve.org/CVERecord?id=CVE-2023-34062 Référence CVE CVE-2023-3446 https://www.cve.org/CVERecord?id=CVE-2023-3446 Référence CVE CVE-2023-34462 https://www.cve.org/CVERecord?id=CVE-2023-34462 Référence CVE CVE-2023-3611 https://www.cve.org/CVERecord?id=CVE

Official advisory ↗
CERT-FR · French · CERTFR-2023-AVI-1007Multiples vulnérabilités dans les produits IBM

CVERecord?id=CVE-2020-14155 Référence CVE CVE-2022-3171 https://www.cve.org/CVERecord?id=CVE-2022-3171 Référence CVE CVE-2022-3509 https://www.cve.org/CVERecord?id=CVE-2022-3509 Référence CVE CVE-2022-3510 https://www.cve.org/CVERecord?id=CVE-2022-3510 Référence CVE CVE-2022-37434 https://www.cve.org/CVERecord?id=CVE-2022-37434 Référence CVE CVE-2023-1370 https://www.cve.org/CVERecord?id=CVE-2023-1370 Référence CVE CVE-2023-28523 https://www.cve.org/CVERecord?id=CVE-2023-28523 Référence CVE CVE-2023-28526 https://www.cve.org/CVERecord?id=CVE-2023-28526 Référence CVE CVE-2023-28527 https://www.cve.org/CVERecord?id=CVE-2023-28527 Référence CVE CVE-2023-32731 https://www.cve.org/CVERecord?id=CVE-2023-32731 Référence CVE CVE-2023-34462 https://www.cve.org/CVERecord?id=CVE-2023-34462 Référence CVE CVE-2023-38003 https://www.cve.org/CVERecord?id=CVE-2023-38003 Référence CVE CVE-2023-43642 https://www.cve.org/CVERecord?id=CVE-2023-43642 Référence CVE CVE-2023-44270 https://www.cve.org/CVERecord?id=CVE-2023-44270 Référence CVE CVE-2023-45133 https://www.cve.org/CVERecord?id=CVE-2023-45133 Gestion détaillée du document le 08 décembre 2023 Version initiale Alertes Avis Bulletins d’actualités Mentions légales Conditions générales À propos Contact cyber.gouv.fr service-public.fr legifrance.gouv.fr info.go

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2023-008068gRPC における脆弱性

gRPC には、不特定の脆弱性が存在します。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Patch available
Affected
Fixed
Action
To install this SUSE Security Update use the SUSE recommended installation methods like YaST online_update or "zypper patch".
Workaround
No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04

Evidence and provenance

Published 9 Jun 2023 · Last source change 26 Sept 2024, 19:12 UTC · CWE-440 · Expected Behavior Violation

CVE recordCVE.org · 5.1
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2023-2030
Product sourceVendor CSAF · SUSE Product Security Team
Remediation sourceVendor CSAF · SUSE Product Security Team
CWE sourceCNA
NVD statusNVD modified after enrichment

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗

No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.

Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
CVE published
Fixed release or patch reference recorded
ENISA EUVD · EUVD-2023-2030↗Vendor CSAF · SUSE Product Security Team↗CVE authority or vendor reference↗Patch or update reference↗Official CVE record (CNA and ADP data)↗NVD record↗
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2023-32731 · cve.blacktree.nl