Vulnerability in Codeready Linux Builder Eus (CVE-2023-5868, CVSS 4.3)

Summary

Vulnerability in Codeready Linux Builder Eus (CVE-2023-5868). Risk of unauthorized operations or information disclosure.

Original description

The description as published by the source.

A memory disclosure vulnerability was found in PostgreSQL that allows remote users to access sensitive information by exploiting certain aggregate function calls with 'unknown'-type arguments. Handling 'unknown'-type values from string literals without type designation can disclose bytes, potentially revealing notable and confidential information. This issue exists due to excessive data output in aggregate function calls, enabling remote users to read some portion of system memory.

Source: NIST National Vulnerability Database NVD

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2023-5868 has been found in Codeready Linux Builder Eus.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Codeready Linux Builder Eus CVE-2023-5868" on the vendor's site.

CVE-2023-5868 (Codeready Linux Builder Eus) — CWE-686 / CVSS v3 4.3
Attack vector: remote (network-reachable) / no user interaction
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-686) exists in Codeready Linux Builder Eus.

📍 Affected scope

Check the vendor advisory for the affected versions of Codeready Linux Builder Eus.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
Audit SBOM/dependencies for affected components.
```
資産台帳・SBOM・依存マニフェストで Codeready Linux Builder Eus を使っているサービスとバージョンを洗い出す。
2
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami postgresql

[{"type":"SEMVER","events":[{"introduced":"11.0.0"},{"fixed":"11.22.0"},{"introduced":"12.0.0"},{"fixed":"12.17.0"},{"introduced":"13.0.0"},{"fixed":"13.13.0"},{"introduced":"14.0.0"},{"fixed":"14.10.0"},{"introduced":"15.0.0"},{"fixed":"15.5.0"},{"introduced":"16.0.0"},{"fixed":"16.0.1"}]}]

Fix status by distribution

Fixed packages published by each distribution for this CVE

Debian DEBIAN-CVE-2023-5868 postgresql-13 Fixed in: 13.13-0+deb11u1