3.6 Low
CVSS2
Attack Vector
LOCAL
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
NONE
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:L/AC:L/Au:N/C:N/I:P/A:P
7.1 High
CVSS3
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
0.0004 Low
EPSS
Percentile
12.7%
abeluck reports:
A flaw was found in Ansible Base when using the aws_ssm connection plugin as garbage collector is not happening after playbook run is completed.
Files would remain in the bucket exposing the data.
This issue affects directly data confidentiality.
A flaw was found in Ansible Base when using the aws_ssm connection plugin as there is no namespace separation for file transfers.
Files are written directly to the root bucket, making possible to have collisions when running multiple ansible processes.
This issue affects mainly the service availability.
OS | Version | Architecture | Package | Version | Filename |
---|---|---|---|---|---|
FreeBSD | any | noarch | py37-ansible | <= 7.2.0 | UNKNOWN |
FreeBSD | any | noarch | py38-ansible | <= 7.2.0 | UNKNOWN |
FreeBSD | any | noarch | py39-ansible | <= 7.2.0 | UNKNOWN |
FreeBSD | any | noarch | py310-ansible | <= 7.2.0 | UNKNOWN |
FreeBSD | any | noarch | py311-ansible | <= 7.2.0 | UNKNOWN |
3.6 Low
CVSS2
Attack Vector
LOCAL
Attack Complexity
LOW
Authentication
NONE
Confidentiality Impact
NONE
Integrity Impact
PARTIAL
Availability Impact
PARTIAL
AV:L/AC:L/Au:N/C:N/I:P/A:P
7.1 High
CVSS3
Attack Vector
LOCAL
Attack Complexity
LOW
Privileges Required
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality Impact
NONE
Integrity Impact
HIGH
Availability Impact
HIGH
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H
0.0004 Low
EPSS
Percentile
12.7%