CVE-2011-0466
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 · uneditedThe API in SUSE openSUSE Build Service (OBS) 2.0.x before 2.0.8 and 2.1.x before 2.1.6 allows attackers to bypass intended write-access restrictions and modify a (1) package or (2) project via unspecified vectors.
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 confidenceThe openSUSE Build Service API fails to enforce write-access controls, allowing authenticated or unauthenticated attackers to modify packages and projects they should not have permission to alter. This is an authorization bypass in the API layer affecting versions 2.0.x before 2.0.8 and 2.1.x before 2.1.6.
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= 2.0= 2.0.0= 2.0.1= 2.0.2= 2.0.3= 2.0.4= 2.0.5= 2.0.6= 2.0.7= 2.0.16= 2.0.103= 2.0.104CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:N/I:P/A:P
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed openSUSE Build Service versionQuery the package manager for the obs-server package version (e.g., rpm -qa | grep obs-server or dpkg -l | grep obs-server). Alternatively, check the API endpoint /build/_pacakge or consult the configuration file in /etc/buildservice or the version file in the application directory.Affected if The installed version is 2.0.x before 2.0.8, or 2.1.x before 2.1.6, or matches one of the listed affected versions (2.0, 2.0.0-2.0.7, 2.0.16, 2.0.103, 2.0.104).
-
Confirm the API component is enabledCheck if the OBS API service is running and listening on its configured port (typically port 80 or 443 for webui, port 5252 for the API daemon). Use commands like netstat -tlnp or ss -tlnp to list listening services, or check the obs-api service status if using systemd.Affected if The API daemon (obs-api) is running and accepting connections.
-
Verify the API is network-accessibleAttempt to reach the API endpoint locally (curl http://localhost:5252 or the configured API port) or check firewall rules and network configuration to determine if the API port is exposed to network clients.Affected if The API port is open and reachable from network clients (authenticated or unauthenticated).
-
Check for write-access control enforcement in API requestsReview API access control logs or attempt a controlled test request to modify a package or project using an account without permissions. Examine the API configuration files (typically in /etc/buildservice or /srv/obs/build) for the enforce_permissions or authorization settings.Affected if The API allows write operations to packages or projects without proper authorization validation, or the enforce_permissions setting is missing or disabled.
A system is affected if it runs an openSUSE Build Service version 2.0.x before 2.0.8 or 2.1.x before 2.1.6 with the API component enabled and accessible, where write-access controls are not being enforced.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to openSUSE Build Service version 2.0.8, 2.1.6, or later to obtain the patch that corrects the access control logic in the API.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-0466 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2011-0466 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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