dbcve.org
Debian LinuxOperating system · Debian

CVE-2020-8020

MEDIUM · 6.1 CVSS v3.1 Published 2020-05-13
Fix available
A fix is available. Upgrade to 2020-05-13 or later.
See remediation →
68/100
Remediation priority · Elevated
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 Improper Neutralization of Input During Web Page Generation vulnerability in open-build-service allows remote attackers to store arbitrary JS code to cause XSS. This issue affects: openSUSE open-build-service versions prior to 7cc32c8e2ff7290698e101d9a80a9dc29a5500fb.

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 · high confidence

A stored XSS vulnerability in open-build-service allows remote attackers to inject arbitrary JavaScript code through unsanitized user input that gets rendered in web pages, enabling execution in victims' browsers.

MitigationUpgrade to version 7cc32c8e2ff7290698e101d9a80a9dc29a5500fb or later which contains the fix; alternatively, implement proper input sanitization and output encoding for all user-supplied data rendered in web pages.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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:= 9.0
Open Build ServiceApplication
Affected:< 2020-05-13

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
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Open Build Service is installed
    Check for OBS installation by looking for the 'obs-api' or 'open-build-service' packages, or by searching for OBS processes running on common web ports (80, 443, 3000, 4000)
    Affected if Open Build Service is installed and running a version below 2020-05-13 or before commit 7cc32c8e2ff7290698e101d9a80a9dc29a5500fb
  2. Determine the installed OBS version
    Run package manager query (dpkg -l obs-server or rpm -q obs-server) or check the OBS API version endpoint if the web interface is accessible
    Affected if Version is earlier than the 2020-05-13 release or commit 7cc32c8e2ff7290698e101d9a80a9dc29a5500fb
  3. Confirm the OBS web interface is enabled
    Verify the web frontend service (typically obswebui) is active and accessible on the network; check /etc/sysconfig/obs-server or similar configuration for WEBUI_ENABLE or API_URL settings
    Affected if The web interface is enabled and exposed, allowing user-supplied content to be rendered in browser pages
  4. Inspect OBS configuration for input handling
    Review OBS configuration files for web template settings and check whether input sanitization or output encoding is explicitly disabled
    Affected if Default configuration is in place without custom sanitization modifications (the vulnerability exists in default configurations prior to the fix)
  5. Check application logs for XSS indicators
    Review OBS web access logs and application logs for suspicious script tags or unusual JavaScript in user-generated fields such as project names, package descriptions, or user comments
    Affected if Evidence of injected script tags or anomalous JavaScript appears in logs or rendered user content

You are affected if Open Build Service is installed with the web interface enabled and the version predates the 2020-05-13 fix commit.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to 2020-05-13 or later
Fixed in 2020-05-13
Interim mitigation

Upgrade to version 7cc32c8e2ff7290698e101d9a80a9dc29a5500fb or later which contains the fix; alternatively, implement proper input sanitization and output encoding for all user-supplied data rendered in web pages.

Fix this in Debian Linux Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-8020 — 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-2020-8020 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