# CVE-2014-1428: uuid.uuid1() is not suitable as an unguessable identifier/token

> Attackers can brute-force file storage keys in Ubuntu MAAS to access unauthorized files due to weak identifier generation.

- **Severity:** Low 2.0 (`CVSS:3.0/AV:A/AC:H/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Apr 2019
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-qq47-q6fw-c7qm

## What is CVE-2014-1428?

CVE-2014-1428 is a low-severity vulnerability in Ubuntu MAAS, published on 22 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability in generate_filestorage_key of Ubuntu MAAS allows an attacker to brute-force filenames. This issue affects Ubuntu MAAS versions prior to 1.9.2.

Weakness: CWE-254

## Which versions are affected by CVE-2014-1428?

It affects 1 product.


Products: Canonical Metal as a Service.

## How do I fix CVE-2014-1428?

No fix has been published for CVE-2014-1428 yet. Limit exposure of the affected software until one is available.

## Is CVE-2014-1428 being exploited?

There is no known exploitation of CVE-2014-1428 in the wild and no public exploit code.

## Other vulnerabilities in Ubuntu MAAS

- [CVE-2024-6107](https://insights.sbomify.com/CVE-2024-6107/): Auth bypass in MAAS (critical 9.6)
- [CVE-2014-1427](https://insights.sbomify.com/CVE-2014-1427/): MAAS API vulnerable to CSRF attack (critical 9.6)
- [CVE-2014-1426](https://insights.sbomify.com/CVE-2014-1426/): get_file_by_name does not check owner (high 8.6)
- [CVE-2015-1320](https://insights.sbomify.com/CVE-2015-1320/): Probe-and-enlist for SeaMicro chassis writes password to the log (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-1428 and fix it if it is affected.

What it is: CVE-2014-1428 is a low-severity vulnerability in Ubuntu MAAS, published on 22 Apr 2019. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-1428 in the wild and no public exploit code.

Affected product: Ubuntu MAAS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2014-1428/ (Markdown: https://insights.sbomify.com/CVE-2014-1428/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2014-1428
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2014-1428
- OSV: https://osv.dev/vulnerability/CVE-2014-1428

---
From sbomify Insights: https://insights.sbomify.com/CVE-2014-1428/
Summaries are generated and may contain mistakes; the official description above is the record.