Explore our new Cybersecurity Terms Glossary, explained by our experts.
Cybersecurity Terms Glossary
JTAG and UART are hardware debug and serial interfaces built into embedded boards. Left enabled in production, they hand an attacker a console or direct access to memory.

What Are JTAG and UART Interfaces?
Open almost any connected product and you will find a row of unpopulated pads or a small header near the processor. Those are the interfaces the engineering team used to bring the board up: UART for a text console, JTAG for halting the processor and reading memory. They are indispensable during development and, far too often, still active on the unit a customer buys.
A universal asynchronous receiver-transmitter is a two-wire serial link — transmit, receive, and a shared ground. On embedded Linux devices it usually carries the bootloader output and then a login prompt or, in a surprising number of products, a root shell with no password at all.
Finding it is straightforward. A multimeter identifies ground and the 3.3 V rail; the transmit pin idles high and shows activity on power-up, which a logic analyser confirms. Connect a USB-to-serial adapter, open a terminal at 115,200 baud (57,600 and 9,600 are the other common rates) and watch the boot log. Even without a shell, that log is valuable: kernel version, partition layout, hardware revision, and frequently the firmware download URL.
The bigger prize is the bootloader. Interrupting U-Boot during its countdown gives a command prompt where you can print the environment, change the kernel command line to init=/bin/sh, and boot straight to a root shell, or dump flash partitions over the same connection.
JTAG, standardised as IEEE 1149.1, was designed for manufacturing test and became the universal debug interface. Its test access port uses four signals — TCK, TMS, TDI, and TDO, plus an optional reset — and ARM’s two-pin Serial Wire Debug is a compact variant of the same idea.
Where UART gives you whatever the software chooses to print, JTAG gives you the silicon: halt the core, read and write any address, single-step instructions, set breakpoints, and read or reprogram internal flash. Encryption keys sitting in RAM are readable, secure boot checks can be patched after they have run, and firmware that no external chip holds can be dumped in full.
Identifying the pins on an unlabelled board is the usual obstacle. A JTAGulator or a Raspberry Pi running JTAGenum brute-forces candidate pin combinations until the scan chain responds; from there OpenOCD with a cheap FT2232 adapter or a Segger J-Link handles the session.
These interfaces defeat controls that look solid from the network side. An attacker with a device in hand can:
Because the keys recovered are usually fleet-wide rather than per-device, one physical compromise scales to every unit. That is the argument for a secure element and for per-device identity.
Design review should treat debug access as a deliberate decision with a documented state for production units, in the same way that threat modelling treats any other interface. Our Hardware Penetration Test Services test exactly this, on production samples rather than development boards.
Identify ground with a multimeter in continuity mode against a shield or connector shell, then look for a pin sitting at a steady 3.3 V that drops into rapid activity during boot: that is transmit. Receive is usually adjacent and idles high with no traffic. A logic analyser confirms the signal and lets software such as PulseView detect the baud rate automatically.
It removes the easiest route but not every route. An attacker can still read external flash with a clip, remove the chip entirely, or attempt fault injection to re-enable debug. Disabling JTAG should sit alongside secure boot, encrypted external storage, and hardware-held keys, so that no single physical technique yields anything useful on its own.
They provide similar debug capability with different wiring. JTAG uses at least four signals and supports chaining several devices on one scan chain, which suits complex boards and boundary scan testing. Serial Wire Debug is an ARM-specific two-pin alternative that saves package pins on small microcontrollers. Many ARM parts expose both, and the security implications are identical.
Not directly; both require physical contact with the board. The practical exception is a product that exposes a debug console over the network or over USB, which some developers leave enabled for convenience. Those should be treated as the same risk as a physical header, because they give the same access without requiring anyone to open the enclosure.
You May Be Interested In These
We use a few cookies that are needed to make this website work, and they are always on. We would also like to set analytics cookies, to see which pages are useful; functional cookies, so that our live chat works; and advertising cookies, to measure our campaigns. We will not set any of those until you say yes, and you can change your mind at any time from the Cookie Settings link in the footer.
Choose the cookies you are happy for us to use. Strictly necessary cookies are always on; everything else is off until you turn it on.
These cookies keep the website working: they hold your security checks, your form submissions and the choice you make here. The site cannot run without them, so they are always on.
These let our live chat open and remember your conversation, and let the newsletter sign-up work. Switch them off and the chat window will not appear.
These tell us which pages are read and how people find us, so that we can improve the site. The reports are about groups of visitors, never about you personally.
These let us measure our advertising and show you our adverts on other websites, such as LinkedIn, Google and Meta. Switch them off and you will still see adverts, but they will be less relevant.