CVE-2021-3709 : Detail

CVE-2021-3709

6.5
/
Medium
Directory Traversal
A01-Broken Access Control
0.05%V3
Local
2021-10-01
02h35 +00:00
2024-09-16
23h31 +00:00
CVE.org
NVD
Notifications for a CVE
Stay informed of any changes for a specific CVE.
Notifications manage

CVE Descriptions

Apport file permission bypass through emacs byte compilation errors

Function check_attachment_for_errors() in file data/general-hooks/ubuntu.py could be tricked into exposing private data via a constructed crash file. This issue affects: apport 2.14.1 versions prior to 2.14.1-0ubuntu3.29+esm8; 2.20.1 versions prior to 2.20.1-0ubuntu2.30+esm2; 2.20.9 versions prior to 2.20.9-0ubuntu7.26; 2.20.11 versions prior to 2.20.11-0ubuntu27.20; 2.20.11 versions prior to 2.20.11-0ubuntu65.3;

CVE Informations

Related Weaknesses

CWE-ID Weakness Name Source
CWE-538 Insertion of Sensitive Information into Externally-Accessible File or Directory
The product places sensitive information into files or directories that are accessible to actors who are allowed to have access to the files, but not to the sensitive information.
CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.

Metrics

Metrics Score Severity CVSS Vector Source
V3.1 6.5 MEDIUM CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Changed

An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.
V3.1 5.5 MEDIUM CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Base: Exploitabilty Metrics

The Exploitability metrics reflect the characteristics of the thing that is vulnerable, which we refer to formally as the vulnerable component.

Attack Vector

This metric reflects the context by which vulnerability exploitation is possible.

Local

The vulnerable component is not bound to the network stack and the attacker’s path is via read/write/execute capabilities.

Attack Complexity

This metric describes the conditions beyond the attacker’s control that must exist in order to exploit the vulnerability.

Low

Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success when attacking the vulnerable component.

Privileges Required

This metric describes the level of privileges an attacker must possess before successfully exploiting the vulnerability.

Low

The attacker requires privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.

User Interaction

This metric captures the requirement for a human user, other than the attacker, to participate in the successful compromise of the vulnerable component.

None

The vulnerable system can be exploited without interaction from any user.

Base: Scope Metrics

The Scope metric captures whether a vulnerability in one vulnerable component impacts resources in components beyond its security scope.

Scope

Formally, a security authority is a mechanism (e.g., an application, an operating system, firmware, a sandbox environment) that defines and enforces access control in terms of how certain subjects/actors (e.g., human users, processes) can access certain restricted objects/resources (e.g., files, CPU, memory) in a controlled manner. All the subjects and objects under the jurisdiction of a single security authority are considered to be under one security scope. If a vulnerability in a vulnerable component can affect a component which is in a different security scope than the vulnerable component, a Scope change occurs. Intuitively, whenever the impact of a vulnerability breaches a security/trust boundary and impacts components outside the security scope in which vulnerable component resides, a Scope change occurs.

Unchanged

An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.

Base: Impact Metrics

The Impact metrics capture the effects of a successfully exploited vulnerability on the component that suffers the worst outcome that is most directly and predictably associated with the attack. Analysts should constrain impacts to a reasonable, final outcome which they are confident an attacker is able to achieve.

Confidentiality Impact

This metric measures the impact to the confidentiality of the information resources managed by a software component due to a successfully exploited vulnerability.

High

There is a total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.

Integrity Impact

This metric measures the impact to integrity of a successfully exploited vulnerability. Integrity refers to the trustworthiness and veracity of information.

None

There is no loss of integrity within the impacted component.

Availability Impact

This metric measures the impact to the availability of the impacted component resulting from a successfully exploited vulnerability.

None

There is no impact to availability within the impacted component.

Temporal Metrics

The Temporal metrics measure the current state of exploit techniques or code availability, the existence of any patches or workarounds, or the confidence in the description of a vulnerability.

Environmental Metrics

These metrics enable the analyst to customize the CVSS score depending on the importance of the affected IT asset to a user’s organization, measured in terms of Confidentiality, Integrity, and Availability.

 [email protected]
V2 2.1 AV:L/AC:L/Au:N/C:P/I:N/A:N [email protected]

EPSS

EPSS is a scoring model that predicts the likelihood of a vulnerability being exploited.

EPSS Score

The EPSS model produces a probability score between 0 and 1 (0 and 100%). The higher the score, the greater the probability that a vulnerability will be exploited.

EPSS Percentile

The percentile is used to rank CVE according to their EPSS score. For example, a CVE in the 95th percentile according to its EPSS score is more likely to be exploited than 95% of other CVE. Thus, the percentile is used to compare the EPSS score of a CVE with that of other CVE.
EPSS First.org

Products Mentioned

Configuraton 0

Canonical>>Apport >> Version 2.14.1-0ubuntu1

Canonical>>Apport >> Version 2.14.1-0ubuntu2

Canonical>>Apport >> Version 2.14.1-0ubuntu3

Canonical>>Apport >> Version 2.14.1-0ubuntu3.1

Canonical>>Apport >> Version 2.14.1-0ubuntu3.2

Canonical>>Apport >> Version 2.14.1-0ubuntu3.3

Canonical>>Apport >> Version 2.14.1-0ubuntu3.4

Canonical>>Apport >> Version 2.14.1-0ubuntu3.5

Canonical>>Apport >> Version 2.14.1-0ubuntu3.6

Canonical>>Apport >> Version 2.14.1-0ubuntu3.7

Canonical>>Apport >> Version 2.14.1-0ubuntu3.8

Canonical>>Apport >> Version 2.14.1-0ubuntu3.9

Canonical>>Apport >> Version 2.14.1-0ubuntu3.10

Canonical>>Apport >> Version 2.14.1-0ubuntu3.11

Canonical>>Apport >> Version 2.14.1-0ubuntu3.12

Canonical>>Apport >> Version 2.14.1-0ubuntu3.13

Canonical>>Apport >> Version 2.14.1-0ubuntu3.14

Canonical>>Apport >> Version 2.14.1-0ubuntu3.15

Canonical>>Apport >> Version 2.14.1-0ubuntu3.16

Canonical>>Apport >> Version 2.14.1-0ubuntu3.17

Canonical>>Apport >> Version 2.14.1-0ubuntu3.18

Canonical>>Apport >> Version 2.14.1-0ubuntu3.19

Canonical>>Apport >> Version 2.14.1-0ubuntu3.20

Canonical>>Apport >> Version 2.14.1-0ubuntu3.21

Canonical>>Apport >> Version 2.14.1-0ubuntu3.23

Canonical>>Apport >> Version 2.14.1-0ubuntu3.24

Canonical>>Apport >> Version 2.14.1-0ubuntu3.25

Canonical>>Apport >> Version 2.14.1-0ubuntu3.27

Canonical>>Apport >> Version 2.14.1-0ubuntu3.28

Canonical>>Apport >> Version 2.14.1-0ubuntu3.29

Canonical>>Apport >> Version 2.14.1-0ubuntu3.29\+esm7

Canonical>>Ubuntu_linux >> Version 14.04

Configuraton 0

Canonical>>Apport >> Version 2.20.1-0ubuntu1

Canonical>>Apport >> Version 2.20.1-0ubuntu2

Canonical>>Apport >> Version 2.20.1-0ubuntu2.1

Canonical>>Apport >> Version 2.20.1-0ubuntu2.2

Canonical>>Apport >> Version 2.20.1-0ubuntu2.4

Canonical>>Apport >> Version 2.20.1-0ubuntu2.5

Canonical>>Apport >> Version 2.20.1-0ubuntu2.6

Canonical>>Apport >> Version 2.20.1-0ubuntu2.7

Canonical>>Apport >> Version 2.20.1-0ubuntu2.8

Canonical>>Apport >> Version 2.20.1-0ubuntu2.9

Canonical>>Apport >> Version 2.20.1-0ubuntu2.10

Canonical>>Apport >> Version 2.20.1-0ubuntu2.12

Canonical>>Apport >> Version 2.20.1-0ubuntu2.13

Canonical>>Apport >> Version 2.20.1-0ubuntu2.14

Canonical>>Apport >> Version 2.20.1-0ubuntu2.15

Canonical>>Apport >> Version 2.20.1-0ubuntu2.16

Canonical>>Apport >> Version 2.20.1-0ubuntu2.17

Canonical>>Apport >> Version 2.20.1-0ubuntu2.18

Canonical>>Apport >> Version 2.20.1-0ubuntu2.19

Canonical>>Apport >> Version 2.20.1-0ubuntu2.20

Canonical>>Apport >> Version 2.20.1-0ubuntu2.21

Canonical>>Apport >> Version 2.20.1-0ubuntu2.22

Canonical>>Apport >> Version 2.20.1-0ubuntu2.23

Canonical>>Apport >> Version 2.20.1-0ubuntu2.25

Canonical>>Apport >> Version 2.20.1-0ubuntu2.26

Canonical>>Apport >> Version 2.20.1-0ubuntu2.27

Canonical>>Apport >> Version 2.20.1-0ubuntu2.28

Canonical>>Apport >> Version 2.20.1-0ubuntu2.30

Canonical>>Apport >> Version 2.20.1-0ubuntu2.30\+esm1

Canonical>>Ubuntu_linux >> Version 16.04

Configuraton 0

Canonical>>Apport >> Version 2.20.9-0ubuntu1

Canonical>>Apport >> Version 2.20.9-0ubuntu2

Canonical>>Apport >> Version 2.20.9-0ubuntu3

Canonical>>Apport >> Version 2.20.9-0ubuntu4

Canonical>>Apport >> Version 2.20.9-0ubuntu5

Canonical>>Apport >> Version 2.20.9-0ubuntu6

Canonical>>Apport >> Version 2.20.9-0ubuntu7

Canonical>>Apport >> Version 2.20.9-0ubuntu7.1

Canonical>>Apport >> Version 2.20.9-0ubuntu7.2

Canonical>>Apport >> Version 2.20.9-0ubuntu7.3

Canonical>>Apport >> Version 2.20.9-0ubuntu7.4

Canonical>>Apport >> Version 2.20.9-0ubuntu7.5

Canonical>>Apport >> Version 2.20.9-0ubuntu7.6

Canonical>>Apport >> Version 2.20.9-0ubuntu7.7

Canonical>>Apport >> Version 2.20.9-0ubuntu7.8

Canonical>>Apport >> Version 2.20.9-0ubuntu7.9

Canonical>>Apport >> Version 2.20.9-0ubuntu7.10

Canonical>>Apport >> Version 2.20.9-0ubuntu7.11

Canonical>>Apport >> Version 2.20.9-0ubuntu7.12

Canonical>>Apport >> Version 2.20.9-0ubuntu7.13

Canonical>>Apport >> Version 2.20.9-0ubuntu7.14

Canonical>>Apport >> Version 2.20.9-0ubuntu7.15

Canonical>>Apport >> Version 2.20.9-0ubuntu7.16

Canonical>>Apport >> Version 2.20.9-0ubuntu7.17

Canonical>>Apport >> Version 2.20.9-0ubuntu7.18

Canonical>>Apport >> Version 2.20.9-0ubuntu7.19

Canonical>>Apport >> Version 2.20.9-0ubuntu7.20

Canonical>>Apport >> Version 2.20.9-0ubuntu7.21

Canonical>>Apport >> Version 2.20.9-0ubuntu7.23

Canonical>>Apport >> Version 2.20.9-0ubuntu7.24

Canonical>>Ubuntu_linux >> Version 18.04

Configuraton 0

Canonical>>Apport >> Version 2.20.11-0ubuntu8

Canonical>>Apport >> Version 2.20.11-0ubuntu9

Canonical>>Apport >> Version 2.20.11-0ubuntu10

Canonical>>Apport >> Version 2.20.11-0ubuntu11

Canonical>>Apport >> Version 2.20.11-0ubuntu12

Canonical>>Apport >> Version 2.20.11-0ubuntu13

Canonical>>Apport >> Version 2.20.11-0ubuntu14

Canonical>>Apport >> Version 2.20.11-0ubuntu15

Canonical>>Apport >> Version 2.20.11-0ubuntu16

Canonical>>Apport >> Version 2.20.11-0ubuntu17

Canonical>>Apport >> Version 2.20.11-0ubuntu18

Canonical>>Apport >> Version 2.20.11-0ubuntu19

Canonical>>Apport >> Version 2.20.11-0ubuntu20

Canonical>>Apport >> Version 2.20.11-0ubuntu21

Canonical>>Apport >> Version 2.20.11-0ubuntu22

Canonical>>Apport >> Version 2.20.11-0ubuntu23

Canonical>>Apport >> Version 2.20.11-0ubuntu24

Canonical>>Apport >> Version 2.20.11-0ubuntu25

Canonical>>Apport >> Version 2.20.11-0ubuntu26

Canonical>>Apport >> Version 2.20.11-0ubuntu27

Canonical>>Apport >> Version 2.20.11-0ubuntu27.2

Canonical>>Apport >> Version 2.20.11-0ubuntu27.3

Canonical>>Apport >> Version 2.20.11-0ubuntu27.4

Canonical>>Apport >> Version 2.20.11-0ubuntu27.5

Canonical>>Apport >> Version 2.20.11-0ubuntu27.6

Canonical>>Apport >> Version 2.20.11-0ubuntu27.7

Canonical>>Apport >> Version 2.20.11-0ubuntu27.8

Canonical>>Apport >> Version 2.20.11-0ubuntu27.9

Canonical>>Apport >> Version 2.20.11-0ubuntu27.10

Canonical>>Apport >> Version 2.20.11-0ubuntu27.11

Canonical>>Apport >> Version 2.20.11-0ubuntu27.12

Canonical>>Apport >> Version 2.20.11-0ubuntu27.13

Canonical>>Apport >> Version 2.20.11-0ubuntu27.14

Canonical>>Apport >> Version 2.20.11-0ubuntu27.16

Canonical>>Apport >> Version 2.20.11-0ubuntu27.17

Canonical>>Apport >> Version 2.20.11-0ubuntu27.18

Canonical>>Ubuntu_linux >> Version 20.04

Configuraton 0

Canonical>>Apport >> Version 2.20.11-0ubuntu28

Canonical>>Apport >> Version 2.20.11-0ubuntu29

Canonical>>Apport >> Version 2.20.11-0ubuntu30

Canonical>>Apport >> Version 2.20.11-0ubuntu31

Canonical>>Apport >> Version 2.20.11-0ubuntu32

Canonical>>Apport >> Version 2.20.11-0ubuntu33

Canonical>>Apport >> Version 2.20.11-0ubuntu34

Canonical>>Apport >> Version 2.20.11-0ubuntu35

Canonical>>Apport >> Version 2.20.11-0ubuntu36

Canonical>>Apport >> Version 2.20.11-0ubuntu37

Canonical>>Apport >> Version 2.20.11-0ubuntu38

Canonical>>Apport >> Version 2.20.11-0ubuntu39

Canonical>>Apport >> Version 2.20.11-0ubuntu40

Canonical>>Apport >> Version 2.20.11-0ubuntu41

Canonical>>Apport >> Version 2.20.11-0ubuntu42

Canonical>>Apport >> Version 2.20.11-0ubuntu43

Canonical>>Apport >> Version 2.20.11-0ubuntu44

Canonical>>Apport >> Version 2.20.11-0ubuntu45

Canonical>>Apport >> Version 2.20.11-0ubuntu46

Canonical>>Apport >> Version 2.20.11-0ubuntu47

Canonical>>Apport >> Version 2.20.11-0ubuntu48

Canonical>>Apport >> Version 2.20.11-0ubuntu49

Canonical>>Apport >> Version 2.20.11-0ubuntu50

Canonical>>Apport >> Version 2.20.11-0ubuntu50.1

Canonical>>Apport >> Version 2.20.11-0ubuntu50.2

Canonical>>Apport >> Version 2.20.11-0ubuntu50.3

Canonical>>Apport >> Version 2.20.11-0ubuntu50.5

Canonical>>Apport >> Version 2.20.11-0ubuntu50.7

Canonical>>Apport >> Version 2.20.11-0ubuntu51

Canonical>>Apport >> Version 2.20.11-0ubuntu52

Canonical>>Apport >> Version 2.20.11-0ubuntu53

Canonical>>Apport >> Version 2.20.11-0ubuntu54

Canonical>>Apport >> Version 2.20.11-0ubuntu55

Canonical>>Apport >> Version 2.20.11-0ubuntu56

Canonical>>Apport >> Version 2.20.11-0ubuntu57

Canonical>>Apport >> Version 2.20.11-0ubuntu58

Canonical>>Apport >> Version 2.20.11-0ubuntu59

Canonical>>Apport >> Version 2.20.11-0ubuntu60

Canonical>>Apport >> Version 2.20.11-0ubuntu61

Canonical>>Apport >> Version 2.20.11-0ubuntu62

Canonical>>Apport >> Version 2.20.11-0ubuntu63

Canonical>>Apport >> Version 2.20.11-0ubuntu64

Canonical>>Apport >> Version 2.20.11-0ubuntu65

Canonical>>Apport >> Version 2.20.11-0ubuntu65.1

Canonical>>Ubuntu_linux >> Version 21.04

References