Ubuntu LinuxOperating system · Canonical
CVE-2013-1058
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 · uneditedmaas-import-pxe-files in MAAS before 13.10 does not verify the integrity of downloaded files, which allows remote attackers to modify these files via a man-in-the-middle (MITM) 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 maas-import-pxe-files component in MAAS before version 13.10 lacks integrity verification (such as checksums or cryptographic signatures) when downloading PXE boot files, allowing remote attackers on the same network path to intercept and modify these files via man-in-the-middle attack. This could result in compromised boot images being deployed to managed nodes.
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
Ubuntu LinuxOperating system
= 12.04= 12.10= 13.04
MaasApplication
<= 12.04.4= 12.04.1= 12.04.2= 12.04.3CVSS 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
- M
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:N/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.
-
Verify MAAS is installedRun command: which maas or dpkg -l | grep maas to check if MAAS package is present on the systemAffected if MAAS package is found on the system, proceed to version check
-
Check installed MAAS versionRun command: maas --version or maas-admin version to determine the exact MAAS version installedAffected if Version is 12.04, 12.04.1, 12.04.2, 12.04.3, 12.04.4, 12.10, or 13.04 (versions below 13.10 are affected)
-
Verify maas-import-pxe-files component existsRun command: which maas-import-pxe-files or dpkg -l | grep maas-import-pxe-files to confirm the PXE import component is installedAffected if The maas-import-pxe-files binary is present on the system
-
Check if PXE boot files have been importedInspect MAAS configuration or run: maas-admin boot-images read to list imported boot images, or check /var/libMAAS/pxe or similar MAAS data directories for downloaded boot filesAffected if PXE boot images have been downloaded and stored without integrity verification (this is the vulnerable condition)
-
Check configuration for integrity verification settingsInspect MAAS configuration files for any checksum or signature verification settings related to PXE file downloads, or check if MAAS 13.10+ integrity features are presentAffected if No integrity verification (checksums, signatures, or equivalent) is configured for downloaded PXE files
If MAAS version is 12.04.x, 12.10, or 13.04 and PXE boot images have been imported without checksum or signature verification, the environment is vulnerable to man-in-the-middle attacks on PXE file downloads.
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 MAAS to version 13.10 or later which implements integrity verification for downloaded PXE files. If immediate upgrade is not possible, ensure download network paths are isolated and trusted to reduce MITM risk.
Fix this in Ubuntu Linux
Scoped from the published advisory
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1058 — 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-2013-1058 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