dbcve.org
Open Build ServiceApplication · Opensuse

CVE-2018-12475

MEDIUM · 5.4 CVSS v3.1 Published 2020-09-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
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 Externally Controlled Reference to a Resource in Another Sphere vulnerability in obs-service-download_files of openSUSE Open Build Service allows authenticated users to generate HTTP request against internal networks and potentially downloading data that is exposed there. This issue affects: openSUSE Open Build Service .

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

The obs-service-download_files component in Open Build Service lacks proper validation of user-supplied URLs, allowing authenticated users to induce the service to make HTTP requests to internal network resources (SSRF). This enables attackers to access data from internal services, intranet resources, or cloud metadata endpoints that should not be externally accessible.

MitigationImplement strict URL allowlist validation in download_files service to restrict downloads to trusted external domains only; additionally, enforce network segmentation to block the build service from accessing internal network ranges (RFC 1918 addresses, cloud metadata endpoints).

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:all versions

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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 download_files service is installed
    Check for the obs-service-download_files package or service binary on the OBS server (typically found in /usr/lib/obs/service/ or via package manager)
    Affected if The download_files service binary exists on the system
  2. Confirm OBS accepts authenticated users
    Review OBS authentication configuration to determine if user accounts can be created and login is permitted (default OBS configuration allows authenticated users)
    Affected if The OBS instance has user authentication enabled and accepts logins from non-admin users
  3. Check download_files service configuration
    Inspect the service configuration files for download_files (typically in /etc/obs/services/ or project service definitions) to see if URL validation or allowlisting is configured
    Affected if No URL allowlist or domain restriction is defined in the service configuration
  4. Verify network isolation
    Review firewall rules or network policies restricting outbound access from the OBS server to internal ranges (192.168.0.0/16, 10.0.0.0/8, 172.16.0.0/12) and cloud metadata endpoints (169.254.169.254)
    Affected if No network segmentation or firewall rules block access to internal network ranges from the OBS server
  5. Inspect recent service executions
    Review OBS service logs for download_files invocations, looking for requests to internal IP ranges or non-public domains
    Affected if Logs show download_files service has been used to access internal network addresses or private IP ranges

A user is affected if the download_files service is installed and the OBS instance allows authenticated user access without URL allowlisting and without network isolation blocking internal resource access.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement strict URL allowlist validation in download_files service to restrict downloads to trusted external domains only; additionally, enforce network segmentation to block the build service from accessing internal network ranges (RFC 1918 addresses, cloud metadata endpoints).

Fix this in Open Build Service Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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