dbcve.org
Metal As A ServiceApplication · Canonical

CVE-2014-1426

HIGH · 7.5 CVSS v3.0 Published 2019-04-22
Fix available
A fix is available. Upgrade to 1.9.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 vulnerability in maasserver.api.get_file_by_name of Ubuntu MAAS allows unauthenticated network clients to download any file. This issue affects: Ubuntu 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 confidence

The maasserver.api.get_file_by_name function in Ubuntu MAAS lacks proper authentication checks, allowing any unauthenticated network client to download arbitrary files from the server by making API requests to this endpoint.

MitigationUpgrade Ubuntu MAAS to version 1.9.2 or later to obtain the patch that adds authentication requirements to the get_file_by_name API function.

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
Affected:< 1.9.2

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Identify installed MAAS version
    Run 'maas --version' or check the package version via dpkg/apt (e.g., dpkg -l | grep maas)
    Affected if The version is below 1.9.2 (e.g., 1.9.1, 1.9.0, 1.8.x, etc.)
  2. Confirm MAAS API service is running
    Check if the maas-region-controller or maas-api service is active: 'systemctl status maas-region-controller' or 'service maas-region-api status'
    Affected if The MAAS API service is exposed on the network and the version is below 1.9.2
  3. Test unauthenticated API access to get_file_by_name
    Make an HTTP request to the API endpoint without credentials: curl http://<maas-server>/api/1.0/files/?filename=test -v
    Affected if The request returns a valid response (200 OK) without requiring authentication
  4. Check authentication configuration for the API
    Review the MAAS configuration file /etc/maas/rackd.conf or /etc/maas/maas.conf for the API authentication settings
    Affected if No authentication requirement is enforced for the files API endpoint

A system is affected if it runs Ubuntu MAAS version below 1.9.2 and exposes the get_file_by_name API endpoint without authentication enforcement.

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
Upgrade available Upgrade to 1.9.2 or later
Fixed in 1.9.2
Interim mitigation

Upgrade Ubuntu MAAS to version 1.9.2 or later to obtain the patch that adds authentication requirements to the get_file_by_name API function.

Fix this in Metal As A Service Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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