PYSEC-2017-21
Vulnerability from pysec - Published: 2017-04-12 22:59 - Updated: 2021-07-05 00:01
VLAI
Details
OpenStack Nova-LXD before 13.1.1 uses the wrong name for the veth pairs when applying Neutron security group rules for instances, which allows remote attackers to bypass intended security restrictions.
Impacted products
| Name | purl | nova-lxd | pkg:pypi/nova-lxd |
|---|
Aliases
{
"affected": [
{
"package": {
"ecosystem": "PyPI",
"name": "nova-lxd",
"purl": "pkg:pypi/nova-lxd"
},
"ranges": [
{
"events": [
{
"introduced": "0"
},
{
"fixed": "1b76cefb92081efa1e88cd8f330253f857028bd2"
}
],
"repo": "https://github.com/openstack/nova-lxd",
"type": "GIT"
},
{
"events": [
{
"introduced": "0"
},
{
"fixed": "13.1.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"0.19.0",
"13.0.0",
"13.0.0.0b2",
"13.0.0.0b3",
"13.1.0"
]
}
],
"aliases": [
"CVE-2017-5936",
"GHSA-6xc7-4cx8-j3xc"
],
"details": "OpenStack Nova-LXD before 13.1.1 uses the wrong name for the veth pairs when applying Neutron security group rules for instances, which allows remote attackers to bypass intended security restrictions.",
"id": "PYSEC-2017-21",
"modified": "2021-07-05T00:01:23.183236Z",
"published": "2017-04-12T22:59:00Z",
"references": [
{
"type": "FIX",
"url": "https://github.com/openstack/nova-lxd/commit/1b76cefb92081efa1e88cd8f330253f857028bd2"
},
{
"type": "WEB",
"url": "https://bugs.launchpad.net/nova-lxd/+bug/1656847"
},
{
"type": "ADVISORY",
"url": "http://www.ubuntu.com/usn/USN-3195-1"
},
{
"type": "WEB",
"url": "http://www.securityfocus.com/bid/96182"
},
{
"type": "WEB",
"url": "http://www.openwall.com/lists/oss-security/2017/02/09/3"
},
{
"type": "ADVISORY",
"url": "https://github.com/advisories/GHSA-6xc7-4cx8-j3xc"
}
]
}
Loading…
Loading…
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.
Loading…