CVE-2018-1000226
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 · uneditedCobbler version Verified as present in Cobbler versions 2.6.11+, but code inspection suggests at least 2.0.0+ or possibly even older versions may be vulnerable contains a Incorrect Access Control vulnerability in XMLRPC API (/cobbler_api) that can result in Privilege escalation, data manipulation or exfiltration, LDAP credential harvesting. This attack appear to be exploitable via "network connectivity". Taking advantage of improper validation of security tokens in API endpoints. Please note this is a different issue than CVE-2018-10931.
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 · low confidenceCobbler's XMLRPC API (/cobbler_api) contains an Incorrect Access Control vulnerability where security tokens are improperly validated across API endpoints. This allows unauthenticated or improperly authenticated remote attackers to escalate privileges, manipulate data, or harvest LDAP credentials. The issue affects version 2.6.11+ and potentially versions back to 2.0.0.
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.0CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Cobbler versionRun 'cobbler --version' or check the package manager (rpm -q cobbler or dpkg -l cobbler)Affected if Version is 2.0.0 or higher through 2.6.10 (or unpatched 2.6.11+) - compare your version against the affected range (>=2.0.0)
-
Verify Cobbler service is runningRun 'systemctl status cobblerd' or 'service cobblerd status' to confirm the daemon is activeAffected if The service is running and the XMLRPC API (/cobbler_api) is available on any network interface
-
Confirm XMLRPC API is network-accessibleCheck cobbler configuration file (typically /etc/cobbler/settings) for 'bind_master' or 'server' settings, and verify the service is listening on non-loopback interfaces (netstat -tlnp | grep cobbler)Affected if The API listens on 0.0.0.0 or a routable IP address rather than only localhost (127.0.0.1)
-
Inspect API access control configurationReview /etc/cobbler/settings for authentication/authorization settings such as 'allow_dynamic_settings', 'xmlrpc_wrap', or custom authentication modules; also check if /var/lib/cobbler/web.ss or similar token files existAffected if No explicit token validation or authentication enforcement is configured for XMLRPC endpoints, or the 'xmlrpc_enable' setting is set without proper access restrictions
-
Test unauthenticated API access (if safe to do so)From an external host, attempt a simple XMLRPC call to the endpoint (e.g., curl -k https://TARGET/cobbler_api with a minimal payload) to verify if authentication is enforcedAffected if The API accepts calls without requiring valid authentication tokens or returns user/LDAP configuration data without credentials
A user is affected if they run Cobbler version 2.0.0 or higher with the XMLRPC API accessible over the network and without proper authentication/authorization controls configured on API endpoints.
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.
dbcve · scopedImplement proper security token validation and enforcement of authentication/authorization checks across all XMLRPC API endpoints. Consider restricting API access via network segmentation or implementing additional authentication layers (e.g., API keys, mutual TLS) if the web interface authentication is separate from API authentication.
Cobbler 2.8.5 or later stable release
- 1. Identify current Cobbler version using 'cobbler --version' or checking the package manager
- 2. For Debian/Ubuntu: Run 'apt-get update && apt-get install cobbler' to upgrade to the latest available version
- 3. For RHEL/CentOS: Run 'yum update cobbler' or 'dnf update cobbler' to upgrade
- 4. Verify the upgrade was successful by checking the new version
- 5. Review Cobbler configuration files (/etc/cobbler/settings) to ensure security settings are appropriate after upgrade
- 6. Restart Cobbler services using 'systemctl restart cobblerd' or 'service cobblerd restart'
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation16.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,136.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-1000226 — 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-2018-1000226 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