Skip to content

Potential manipulation of data displayed and DoS potential attack for budgie-extras budgie-takeabreak applet

Moderate
fossfreedom published GHSA-rvhc-rch9-j943 Dec 14, 2023

Package

budge-takeabreak (python)

Affected versions

> 1.4

Patched versions

v1.7.1

Description

Impact

Data used by the takeabreak budgie applet is stored in a host system location that is accessible to any user who has local access to the system.

The data file format is easily guessable; this potentially allows a local attacker to pre-create this file and have arbitrary string
content displayed instead of the actual "next time". A denial-of-service will also be possible e.g. by placing a FIFO there. Since the applet runs in the same thread for the budgie panel, by crashing the applet this can crash the entire panel.

Patches

The fix has been resolved in a patch release v1.7.1

Workarounds

This issue can be mitigated if there is only one user account on the system and limiting physical access to other users to the host system.

References

None.

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:L

CVE ID

CVE-2023-49345

Weaknesses

No CWEs

Credits