dbcve.org
Debian LinuxOperating system · Debian

CVE-2025-3155

HIGH · 7.4 CVSS v3.1 Published 2025-04-03
No fix yet
No fix has been published. The vendor has not shipped a fixed release or patch. You remain exposed.
See remediation →
81/100
Remediation priority · High
Public exploit Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A flaw was found in Yelp. The Gnome user help application allows the help document to execute arbitrary scripts. This vulnerability allows malicious users to input help documents, which may exfiltrate user files to an external environment.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis
How this class of weakness works · CWE-601

The application redirects the browser to a URL taken from user input without validating it, so an attacker can craft a link on your trusted domain that quietly bounces victims to a malicious site. It is a staple of phishing and token theft. The fix is to allow-list redirect destinations or use indirect reference keys, never a raw user-supplied URL.

General guidance for the open redirect class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Debian LinuxOperating system
Affected:= 11.0
Codeready Linux BuilderApplication
Affected:= 8.0= 9.0
Codeready Linux Builder For Arm64Application
Affected:= 8.0_aarch64= 9.0_aarch64
Codeready Linux Builder For Arm64 EusApplication
Affected:= 8.8_aarch64= 9.2_aarch64= 9.4_aarch64= 9.6_aarch64
Codeready Linux Builder For EusApplication
Affected:= 8.8= 9.2= 9.4
Codeready Linux Builder For Ibm Z SystemsApplication
Affected:= 8.0_s390x= 9.0_s390x
Codeready Linux Builder For Ibm Z Systems EusApplication
Affected:= 8.8_s390x= 9.2_s390x= 9.4_s390x= 9.6_s390x
Codeready Linux Builder For Power Little EndianApplication
Affected:= 8.0_ppc64le= 9.0_ppc64le

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Recommended fix Moderate confidence

Upgrade to the latest patched version of Yelp available in your distribution's security repositories (Debian 11.0 security updates or Red Hat Codeready Linux Builder channel)

  1. 1. Identify the installed Yelp package version on the system using: rpm -qa | grep yelp (RHEL-based) or dpkg -l | grep yelp (Debian-based)
  2. 2. For Debian 11.0 (Bullseye), check for available security updates: apt-get update && apt-cache policy yelp
  3. 3. Apply the security update: apt-get install --upgrade yelp (Debian) or yum update yelp (RHEL)
  4. 4. Verify the patched version is installed: yelp --version or rpm -qa | grep yelp
  5. 5. Restart any running yelp processes to ensure the patch takes effect

Generated from the published advisory — verify against the referenced sources before acting.

No vendor fix exists Debian Linux has not published a patch for this.

There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.

Add your voice

Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.

Can’t wait

We develop and verify an original fix where the vendor hasn’t, from $1,250. Deployed to your staging first — never straight to production.

Scope it with us

See what else the community needs solved on the solutions-needed board.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3155 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3155 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data