Security readout for executives and security teams
Plain-English summary
software-properties could be tricked by a network attacker because it did not properly validate TLS certificates when handling PPAs. If a user added or queried a PPA over an intercepted connection, an attacker could potentially tamper with sensitive repository-related traffic. Sources say this was fixed in software-properties 0.92.
Executive priority
Treat as moderate priority. It is not reported as actively exploited, but it can undermine repository trust during administrative software-source changes, which can create downstream integrity risk if left unresolved.
Technical view
The flaw is CWE-295 improper certificate validation in softwareproperties/ppa.py. Under Python 2, certificates were not checked; under Python 3, checks occurred only when a valid certificate bundle was provided. CVSS 3.1 is 6.8, requiring network position, high attack complexity, and user interaction, with confidentiality and integrity impact.
Likely exposure
Exposure is most likely on Ubuntu systems using vulnerable Canonical software-properties code for PPA operations before the certificate-validation fix. The bundle’s version data is limited and appears inconsistent with the description, so validate installed packages against Canonical guidance and changelogs.
Exploitation context
No KEV listing or cited source in the bundle supports active exploitation. Practical exploitation would require a person-in-the-middle position and user interaction during affected PPA-related activity, which raises difficulty but does not remove risk on untrusted networks.
Researcher notes
The key uncertainty is version mapping: the description says fixed in 0.92, while the affected field lists 0.92. Use the Launchpad bug and merge reference to confirm exact package revisions before declaring exposure or closure.
Mitigation direction
- Upgrade software-properties to a vendor release containing the 0.92 fix or later.
- Confirm the package includes the lp1036839 certificate-validation change.
- Avoid adding or modifying PPAs on untrusted networks until remediated.
- Check Canonical guidance if package version mapping is unclear.
Validation and detection
- Inventory systems with Canonical software-properties installed.
- Verify installed package version and changelog include the certificate-validation fix.
- Review Ubuntu package sources for legacy PPA setup workflows.
- Prioritize systems used on shared, hostile, or untrusted networks.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-295: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2012-0955 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 6.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N1.65.2Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
6.8MediumVector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://launchpad.net/bugs/1036839CVE reference · vendor-advisory, x_refsource_UBUNTU
- https://code.launchpad.net/~cyphermox/software-properties/lp1036839/+merge/119753CVE reference · vendor-advisory, x_refsource_UBUNTU
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Certificate Validation
Improper Certificate Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.