Dark Reading is part of the Informa Tech Division of Informa PLC

This site is operated by a business or businesses owned by Informa PLC and all copyright resides with them.Informa PLC's registered office is 5 Howick Place, London SW1P 1WG. Registered in England and Wales. Number 8860726.

Mobile Security

10/25/2018
12:07 PM
Scott Ferguson
Scott Ferguson
News Analysis-Security Now
50%
50%

Trump's Numerous iPhones Creating Security Headache Report

The New York Times reports that President Donald Trump uses up to three different iPhones and that his habits have left his calls open to spying from China and Russia.

President Donald Trump uses up to three different iPhones during the course of the day, and his calling and security habits are so lax that China and Russian spies routinely listen in on his calls to friends and supporters, according to detailed report in the New York Times.

The report claims that Trump uses at least two different iPhones that have been modified by the National Security Agency, but that he insists on using a third iPhone to call his friends and other acquaintances since the smartphone still allows him to store contact information.

The story, published late Wednesday, October 24, is based on anonymous sources who spoke to the Times.

In the story, Times reporters point out that China is taking advantage of Trump's less-than-secure communications to eavesdrop on various conversations and then use that to craft government policy. Right now, the US and China are in the middle of a trade war, and China's leaders are trying to determine how they can influence US decision making.

(Source: Flickr)
(Source: Flickr)

Russia also appears to have access to these conversations between Trump and his friends, although the report indicates that the country is not running a sophisticated operation compared to the one the Chinese government is conducting.

If true, the report seems to indicate that the NSA and other federal government agencies have a massive BYOD security fail on their hands. As the Times points out, while Trump does not use an unsecured wireless network, the "security of the device ultimately depends on the user, and protecting the president's phones has sometimes proved difficult."

Trump denied the report in typical fashion:

While the NSA has modified two of the three iPhones, Trump has been warned that cellular communications are not safe and the president has been urged to use the secure landline located in his office.

The Times story does note that the NSA did manage to persuade Trump to stop using his pre-presidential Android device, since it's considered less secure. However, the president still insists on balancing three different iPhone throughout the day.

While the story is masterclass in how not to secure end devices within an enterprise -- not to mention the havoc an insider threat can cause -- some have found some humor in the details. For example, the Chinse embassy denied the story in a Tweet, but took aim at the Trump administration's treatment of Huawei, which has run into several problems in the US.

If there's a bright spot in the Times story, it's that the White House security and IT staff can rest easy when it comes to phishing campaigns that target Trump: The president doesn't use email.

Related posts:

— Scott Ferguson is the managing editor of Light Reading and the editor of Security Now. Follow him on Twitter @sferguson_LR.

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
Commentary
Ransomware Is Not the Problem
Adam Shostack, Consultant, Entrepreneur, Technologist, Game Designer,  6/9/2021
Edge-DRsplash-11-edge-ask-the-experts
How Can I Test the Security of My Home-Office Employees' Routers?
John Bock, Senior Research Scientist,  6/7/2021
News
New Ransomware Group Claiming Connection to REvil Gang Surfaces
Jai Vijayan, Contributing Writer,  6/10/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: Zero Trust doesn't have to break your budget!
Current Issue
The State of Cybersecurity Incident Response
In this report learn how enterprises are building their incident response teams and processes, how they research potential compromises, how they respond to new breaches, and what tools and processes they use to remediate problems and improve their cyber defenses for the future.
Flash Poll
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-34202
PUBLISHED: 2021-06-16
There are multiple out-of-bounds vulnerabilities in some processes of D-Link AC2600(DIR-2640) 1.01B04. Ordinary permissions can be elevated to administrator permissions, resulting in local arbitrary code execution. An attacker can combine other vulnerabilities to further achieve the purpose of remot...
CVE-2021-32659
PUBLISHED: 2021-06-16
Matrix-appservice-bridge is the bridging service for the Matrix communication program's application services. In versions 2.6.0 and earlier, if a bridge has room upgrade handling turned on in the configuration (the `roomUpgradeOpts` key when instantiating a new `Bridge` instance.), any `m.room.tombs...
CVE-2020-25755
PUBLISHED: 2021-06-16
An issue was discovered on Enphase Envoy R3.x and D4.x (and other current) devices. The upgrade_start function in /installer/upgrade_start allows remote authenticated users to execute arbitrary commands via the force parameter.
CVE-2020-25754
PUBLISHED: 2021-06-16
An issue was discovered on Enphase Envoy R3.x and D4.x devices. There is a custom PAM module for user authentication that circumvents traditional user authentication. This module uses a password derived from the MD5 hash of the username and serial number. The serial number can be retrieved by an una...
CVE-2020-25753
PUBLISHED: 2021-06-16
An issue was discovered on Enphase Envoy R3.x and D4.x devices with v3 software. The default admin password is set to the last 6 digits of the serial number. The serial number can be retrieved by an unauthenticated user at /info.xml.