Metal As A ServiceApplication · Canonical
CVE-2014-1427
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 · uneditedA vulnerability in the REST API of Ubuntu MAAS allows an attacker to cause a logged-in user to execute commands via cross-site scripting. This issue affects MAAS versions prior to 1.9.2.
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 confidenceCross-site scripting (XSS) vulnerability in Ubuntu MAAS REST API allows authenticated attackers to inject malicious scripts that execute in the context of other logged-in users' sessions, potentially leading to command execution.
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
Metal As A ServiceApplication
< 1.9.2CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if MAAS is installedCheck for the presence of the MAAS package using your system package manager (e.g., dpkg -l | grep maas, rpm -qa | grep maas, or apt list --installed 2>/dev/null | grep maas)Affected if MAAS package is not found on the system, then the system is not affected by this CVE.
-
Determine installed MAAS versionQuery the installed MAAS version using the package manager or the 'maas --version' command if availableAffected if The installed version is lower than 1.9.2 (e.g., 1.8.x, 1.7.x, etc.), indicating the environment is within the affected version range.
-
Verify REST API is accessibleCheck if the MAAS REST API endpoint is exposed and accessible (typically at http://<maas-server>/MAAS/api/ or https://<maas-server>/MAAS/api/)Affected if The REST API is accessible without proper input validation safeguards in place, creating the attack surface for XSS exploitation.
-
Confirm authentication is enabled for APIReview MAAS configuration to confirm that user authentication is required for REST API access (check /etc/maas/maas.conf or equivalent configuration file for authentication settings)Affected if Authenticated users can access the REST API, which is the prerequisite condition for authenticated attackers to inject malicious XSS payloads.
-
Inspect for existing malicious scriptsReview MAAS API logs and session data for any suspicious script tags or unexpected JavaScript references in API request parameters or user-created MAAS objects (nodes, tags, or profiles)Affected if Malicious script tags or encoded XSS payloads are found in API logs or stored MAAS data, indicating the vulnerability has been exploited.
The environment is affected if MAAS is installed with a version lower than 1.9.2 and the REST API is accessible to authenticated users, allowing XSS injection to persist across user sessions.
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 data1.9.2
Upgrade MAAS to version 1.9.2 or later; implement proper input validation and output encoding on all REST API endpoints.
Fix this in Metal As A Service
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-1427 — 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-1427 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