CVE intelligence and bounded remediation

CVE-2023-41054 — LibreY is a fork of LibreX, a framework-less and javascript-free privacy respecting meta search engine

Critical CVSS 9.1

LibreY is a fork of LibreX, a framework-less and javascript-free privacy respecting meta search engine. LibreY is subject to a Server-Side Request Forgery (SSRF) vulnerability in the `image_proxy.php` file of LibreY before commit 8f9b9803f231e2954e5b49987a532d28fe50a627. This vulnerability allows remote attackers to use the server as a proxy to send HTTP GET requests to arbitrary targets and retrieve information in the internal network or conduct Denial-of-Service (DoS) attacks via the `url` parameter. Remote attackers can use the server as a proxy to send HTTP GET requests and retrieve information in the internal network. Remote attackers can also request the server to download large files or chain requests among multiple instances to reduce the performance of the server or even deny access from legitimate users. This issue has been addressed in https://github.com/Ahwxorg/LibreY/pull/31. LibreY hosters are advised to use the latest commit. There are no known workarounds for this vulnerability.

Severity
Critical
CVSS
9.1 (3.1)
Published
2023-09-04
CISA KEV
Not currently listed
Ecosystem
javascript/npm
Weaknesses
CWE-918

Affected products

  • ahwx / librey

Matched remediation archetype

Server-side request forgery and unintended proxying

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory server-side URL fetchers, webhooks, importers, previews, redirects, proxies, and protocol handlers reachable from untrusted input.
  • Map egress paths to internal services, metadata endpoints, loopback, private address space, and privileged control planes.
  • Review DNS resolution, redirect, proxy, credential-forwarding, and URL parsing behavior without requesting sensitive targets.

Remediate safely

  • Replace arbitrary destinations with named integrations or a strict allowlist of schemes, hosts, ports, and paths.
  • Resolve and validate every destination and redirect hop, then enforce egress policy independently of application checks.
  • Remove ambient credentials and sensitive headers from fetchers; apply response size, time, and content limits.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.