nslookup - hit enter with no args or options, prompt advances one line and shows a > operator; then hit ctrl c and normal prompt returns, but now all entries typed at prompt are invisible as though entering a sudo password; commands still execute.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bind9 (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
Bug involving nslookup behaves as follows:
user@machineName:~$ nslookup # Command is entered with no args/options.
> # Redirection operator attempting to prompt user for args/options appears.
user@machineName:~$ # but any commands entered are not visible to the user.
I expected that entering ctrl+c would return a prompt that would function normally - i.e., commands entered would be visible to the user.
This bug could afford a malicious actor already in a target machine the ability to execute commands and engage in privilege escalation.
System Details:
Ubuntu 22.04.4 LTS - Running on a virtual machine (VirtualBox); though I have encountered this bug on an Acer Chromebook that has been repurposed to Run Ubuntu 22.04.4 LTS. I have not encountered this issue on other Debian-based systems of mine.
"apt-cache policy bind9-dnsutils" reports the following:
Installed: 1:9.18.
Candidate: 1:9.18.
Version table:
*** 1:9.18.
500 http://
500 http://
100 /var/lib/
500 http://
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: dnsutils (not installed)
ProcVersionSign
Uname: Linux 6.5.0-25-generic x86_64
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
CasperMD5CheckM
CasperMD5CheckR
CurrentDesktop: ubuntu:GNOME
Date: Tue Apr 30 16:07:15 2024
InstallationDate: Installed on 2024-03-08 (53 days ago)
InstallationMedia: Ubuntu 22.04.4 LTS "Jammy Jellyfish" - Release amd64 (20240220)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
RebootRequiredPkgs: Error: path contained symlinks.
SourcePackage: bind9
UpgradeStatus: No upgrade log present (probably fresh install)
Hello Spencer, thanks for the report. This is pretty common with programs that provide a more "interactive" experience. There's two tools that can help recover from this, reset(1) and stty(1). When this happens, run:
reset
or
stty sane
Both should fix this specific case. But sometimes one or the other one is required to fix your terminal, so it's helpful to know both of them.
Thanks