CAPEC-40: Manipulating Writeable Terminal Devices |
Description This attack exploits terminal devices that allow themselves to be written to by other users. The attacker sends command strings to the target terminal device hoping that the target user will hit enter and thereby execute the malicious command with their privileges. The attacker can send the results (such as copying /etc/passwd) to a known directory and collect once the attack has succeeded. Likelihood Of Attack Typical Severity Execution Flow Explore Identify attacker-writable terminals: Determine if users TTYs are writable by the attacker. | Techniques |
|---|
| Determine the permissions for the TTYs found on the system. Any that allow user write to the TTY may be vulnerable. | | Attempt to write to other user TTYs. This approach could leave a trail or alert a user. |
Exploit Execute malicious commands: Using one or more vulnerable TTY, execute commands to achieve various impacts. | Techniques |
|---|
| Commands that allow reading or writing end user files can be executed. |
Prerequisites
| User terminals must have a permissive access control such as world writeable that allows normal users to control data on other user's terminals. |
Skills Required
[Level: Low] Ability to discover permissions on terminal devices. Of course, brute force can also be used. |
Resources Required
| Access to a terminal on the target network |
Consequences This table specifies different individual consequences associated with the attack pattern. The Scope identifies the security property that is violated, while the Impact describes the negative technical impact that arises if an adversary succeeds in their attack. The Likelihood provides information about how likely the specific consequence is expected to be seen relative to the other consequences in the list. For example, there may be high likelihood that a pattern will be used to achieve a certain impact, but a low likelihood that it will be exploited to achieve a different impact.| Scope | Impact | Likelihood |
|---|
Confidentiality Access Control Authorization | Gain Privileges | | Confidentiality | Read Data | | Confidentiality Integrity Availability | Execute Unauthorized Commands | |
Mitigations
| Design: Ensure that terminals are only writeable by named owner user and/or administrator |
| Design: Enforce principle of least privilege |
Example Instances
"Any system that allows other peers to write directly to its terminal process is vulnerable to this type of attack. If the terminals are available through being over-privileged (i.e. world-writable) or the attacker is an administrator, then a series of commands in this format can be used to echo commands out to victim terminals. "$echo -e "\033[30m\033\132" > /dev/ttyXX where XX is the tty number of the user under attack. This will paste the characters to another terminal (tty). Note this technique works only if the victim's tty is world writable (which it may not be). That is one reason why programs like write(1) and talk(1) in UNIX systems need to run setuid." [REF-1] If the victim continues to hit "enter" and execute the commands, there are an endless supply of vectors available to the attacker, copying files, open up network connections, ftp out to servers, and so on. |
References
[REF-1] G. Hoglund and
G. McGraw. "Exploiting Software: How to Break Code". Addison-Wesley. 2004-02.
|
Content History | Submissions |
|---|
| Submission Date | Submitter | Organization |
|---|
| 2014-06-23 (Version 2.6) | CAPEC Content Team | The MITRE Corporation | | | Modifications |
|---|
| Modification Date | Modifier | Organization |
|---|
| 2017-08-04 (Version 2.11) | CAPEC Content Team | The MITRE Corporation | | Updated Attack_Phases, Description, Description Summary, Related_Vulnerabilities | | 2018-07-31 (Version 2.12) | CAPEC Content Team | The MITRE Corporation | | Updated Attacker_Skills_or_Knowledge_Required, Related_Attack_Patterns, Type (Attack_Pattern -> Relationship) | | 2019-04-04 (Version 3.1) | CAPEC Content Team | The MITRE Corporation | | Updated Related_Weaknesses | | 2020-07-30 (Version 3.3) | CAPEC Content Team | The MITRE Corporation | | Updated Example_Instances | | 2022-09-29 (Version 3.8) | CAPEC Content Team | The MITRE Corporation | | Updated Example_Instances |
More information is available — Please select a different filter.
|