dbcve.org
Open Build ServiceApplication · Opensuse

CVE-2022-21949

HIGH · 8.8 CVSS v3.1 Published 2022-05-03
Fix available
A fix is available. Upgrade to 2.10.13 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 Restriction of XML External Entity Reference vulnerability in SUSE Open Build Service allows remote attackers to reference external entities in certain operations. This can be used to gain information from the server that can be abused to escalate to Admin privileges on OBS. This issue affects: SUSE Open Build Service Open Build Service versions prior to 2.10.13.

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

An XXE (XML External Entity) vulnerability in SUSE Open Build Service allows remote attackers to craft malicious XML requests with external entity references. This enables information disclosure from the server, which can be leveraged to escalate privileges to Admin level on the OBS platform.

MitigationUpgrade SUSE Open Build Service to version 2.10.13 or later to remediate the XXE vulnerability. If immediate patching is not possible, consider disabling XML external entity processing in the XML parser as a compensating control.

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
Open Build ServiceApplication
Affected:< 2.10.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify installed OBS version
    Locate the Open Build Service installation and determine its version number. This may be visible in the package manager, the OBS web interface footer, or the /usr/lib/obs/server directory if you have server access.
    Affected if The version is lower than 2.10.13 (e.g., 2.9.x, 2.10.x versions prior to 2.10.13)
  2. Confirm OBS API is accessible
    Verify that the OBS API endpoint is reachable and responding to requests. The XXE vulnerability is exploitable through the API's XML request handling.
    Affected if The OBS API service is running and accessible over HTTP/HTTPS
  3. Check if XML-based operations are in use
    Determine whether the OBS deployment uses XML-based project configuration, metadata, or API interactions. XXE requires the application to parse XML input.
    Affected if XML files are being processed by the OBS API (such as .xml project files, API requests with XML content-type, or RPM spec file processing)
  4. Verify compensating controls are absent
    If you cannot confirm the version, check whether XML external entity processing has been explicitly disabled in the XML parser configuration.
    Affected if No XML external entity restrictions are configured and the version is unknown or below 2.10.13

You are affected if you are running any version of SUSE Open Build Service below 2.10.13 and the system processes XML input through its API.

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.

dbcve · scoped
Upgrade available Upgrade to 2.10.13 or later
Fixed in 2.10.13
Interim mitigation

Upgrade SUSE Open Build Service to version 2.10.13 or later to remediate the XXE vulnerability. If immediate patching is not possible, consider disabling XML external entity processing in the XML parser as a compensating control.

Recommended fix High confidence

Open Build Service 2.10.13 or later

  1. Identify the current Open Build Service version in use
  2. Review the upgrade notes and release documentation for version 2.10.13
  3. Plan maintenance window as upgrade may require downtime
  4. Back up the OBS database and configuration files
  5. Upgrade OBS to version 2.10.13 or later following the official upgrade guide
  6. Verify the XXE vulnerability is patched by testing XML parsing with external entity references
  7. Confirm all services are running correctly after upgrade

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

Fix this in Open Build Service Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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