Cyber Resilience

CVE-2023-34598

Path Traversal in Gibbonedu Gibbon 25.0.00

Public PoCPath Traversal
Published
29 June 2023
Modified
21 November 2024
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.47 99th percentile
Risk Priority 97 floored blend · peak EPSS

Summary

CVE-2023-34598 is a critical-severity Path Traversal (CWE-22) vulnerability in Gibbonedu Gibbon. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

Gibbon version 25.0.0 contains a local file inclusion vulnerability tracked as CVE-2023-34598 and assigned CWE-22. The flaw permits an attacker to supply crafted input that causes the application to read and return the contents of arbitrary files located inside the Gibbon installation directory, exposing configuration data, source code, or other sensitive resources present on the server.

The CVSS 3.1 score of 9.8 reflects a network-accessible attack that requires no authentication or user interaction. An unauthenticated remote attacker can therefore retrieve file contents that may contain credentials or other material useful for further compromise, resulting in high impact to confidentiality, integrity, and availability.

Public references consist of a GitHub repository containing proof-of-concept material for the issue. The associated EPSS score currently stands at 0.9142 with a recorded peak of 0.9179, indicating a persistently high probability of exploitation.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

Gibbon v25.0.0 is vulnerable to a Local File Inclusion (LFI) where it's possible to include the content of several files present in the installation folder in the server's response.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-45880Same product: Gibbonedu Gibbon
CVE-2025-21048Shared CWE-22
CVE-2026-23939Shared CWE-22
CVE-2024-7145Shared CWE-22
CVE-2023-42225Shared CWE-22
CVE-2024-33109Shared CWE-22
CVE-2023-35016Shared CWE-22
CVE-2025-10723Shared CWE-22
CVE-2023-1163Shared CWE-22
CVE-2024-43996Shared CWE-22

Affected Assets

gibbonedu
gibbon
25.0.00

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)

Validate
Prove the fix (OWASP ASVS)
  • V5.3.2

Likely Mitigating Controls AI

Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.

addresses: CWE-22

Validates pathnames and filenames to prevent traversal outside intended directories.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 partial match
prevents

Patching/maintenance can remediate known path-traversal flaws in deployed software (partial prevention of exploitability) but does nothing to stop the coding defect from being introduced in the first place.

PR.AA-05 none match
prevents

PR.AA-05 defines and reviews access policies but does not address code-level pathname neutralization, so neither direction prevents CWE-22.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing in development catches path traversal via static/dynamic analysis.

prevents

Secure SDLC mandates input validation and path sanitization that directly prevent path traversal.

prevents

Application security requirements include rules for safe file handling and canonicalization.

prevents

Secure architecture principles require least-privilege file access and directory isolation.

prevents

Secure coding standards explicitly forbid unsafe path construction and mandate safe APIs.

mitigates

Information access restriction limits which files an application may read or write.

References