ServicesDrupal extension · Services Project
CVE-2014-9152
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 _user_resource_create function in the Services module 7.x-3.x before 7.x-3.10 for Drupal uses a password of 1 when creating new user accounts, which makes it easier for remote attackers to guess the password via a brute force attack.
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 _user_resource_create function in Drupal's Services module 7.x-3.x before 7.x-3.10 sets a hardcoded default password of '1' when creating new user accounts through the API, allowing remote attackers to easily guess credentials via brute force.
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
ServicesDrupal extension
<= 7.x-3.9CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/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 Services module versionIn Drupal admin, go to Modules page and locate the Services module, or query the system table: SELECT version FROM system WHERE name = 'services' AND type = 'module';Affected if Version is 7.x-3.9 or earlier (7.x-3.9, 7.x-3.8, etc.)
-
Confirm Services module is installedCheck for the presence of the Services module in Drupal's module directory (sites/all/modules/services or sites/all/modules/contrib/services) and verify it is enabled in the database.Affected if Services module is installed and enabled
-
Verify user resource endpoint existsCheck Drupal's services_endpoint table or inspect the Services endpoint configuration to determine if a REST/server endpoint is configured and user resource is exposed.Affected if A Services endpoint is configured with user resource (user resource create) enabled
-
Check API endpoint accessibilityAttempt a HEAD or OPTIONS request to the Services endpoint URL (e.g., /api/user.json or /endpoint/user) to confirm it is accessible over the network.Affected if The user resource endpoint is reachable without authentication or allows anonymous user creation
Environment is affected if Drupal Services module version is 7.x-3.9 or earlier AND a user resource endpoint is exposed and accessible through the Services API.
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 the Services module to version 7.x-3.10 or later, which addresses the hardcoded password issue.
Fix this in Services
Scoped from the published advisory
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-9152 — 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-2014-9152 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