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.

Attacks/Breaches

1/22/2021
05:40 PM
Connect Directly
Twitter
LinkedIn
RSS
E-Mail
50%
50%

Intel Confirms Unauthorized Access of Earnings-Related Data

News likely contributed to slide of over 9% in chipmaker's stock at one point Friday.

Intel shares on Friday at one point dropped by as much as 9% from Thursday evening's close at least partly because of reports the chipmaker was forced to release its Q4, 2020 results a little early because someone illegally accessed earnings-related data from the company.

The Financial Times Thursday quoted Intel CFO George Davis as saying an individual had accessed material pertaining to Intel's financial results from the chipmaker's corporate website before the company's scheduled earnings announcement.

Related Content:

Intel Doubles Down on Emerging Technologies for Sharing and Using Data Securely

Special Report: Understanding Your Cyber Attackers

New From The Edge: How Cybersecurity Newbs Can Start Out on the Right Foot

Specifically, the individual accessed an infographic containing information on the results from a staging area on Intel's PR newsroom site. Upon discovering the illegal access, Intel decided to release its Q4 earnings about six minutes ahead of schedule, the FT reported Davis as saying.

Davis did not offer any further details on how the alleged intruder might have gained access to the infographic on Intel's PR website or whether other information had been illegally accessed as well.

In an emailed statement to Dark Reading, an Intel spokesperson confirmed the incident but said the breach did not result from a network compromise.

"Yesterday, the URL of our earnings infographic was inadvertently made publicly accessible before publication of our earnings and accessed by third parties," the statement said. "Once we became aware of the situation we promptly issued our earnings announcement. Intel's network was not compromised and we have adjusted our process to prevent this in the future."

News of the incident is believed to have at least partially contributed to Intel's stock slide Friday after the company announced what was regarded as a better-than-expected performance in the last quarter of 2020. Even though Intel's Q4 revenues of $20 billion was slight lower than during the same period in 2019, it still beat Wall Street expectations as did the company's net income for the quarter.

"The negative impact on Intel's finances after a hacker gained early access to earnings information from its website is, unfortunately, a sign of why data security has become a boardroom issue," said Max Vetter, chief cyber officer at Immersive Labs, in a statement. "This is a prime example of an attack that affects the entire organization."

The unauthorized access of earnings-related data at Intel is another example of how even large, security- and technology-savvy companies can become victims of breaches and security slip-ups just as easily as smaller organizations. Just last month, for instance, Microsoft disclosed its own network had been infected with malware-laden software updates from SolarWinds even as the company was investigating the breach on behalf of its customers. And security vendor FireEye in December disclosed that attackers had stolen some of its red team tools following an intrusion into its network that came via the malicious SolarWinds update.

"The incident at Intel just adds to the evidence that no organization on earth, public or private, is immune to material harm from breaches," says Hitesh Sheth, president and CEO at Vectra. "We know cybersecurity is a first priority at Intel, so imagine the vulnerabilities at organizations that are less vigilant."

 

Jai Vijayan is a seasoned technology reporter with over 20 years of experience in IT trade journalism. He was most recently a Senior Editor at Computerworld, where he covered information security and data privacy issues for the publication. Over the course of his 20-year ... View Full Bio
 

Recommended Reading:

Comment  | 
Print  | 
More Insights
Comments
Newest First  |  Oldest First  |  Threaded View
News
Former CISA Director Chris Krebs Discusses Risk Management & Threat Intel
Kelly Sheridan, Staff Editor, Dark Reading,  2/23/2021
Edge-DRsplash-10-edge-articles
Security + Fraud Protection: Your One-Two Punch Against Cyberattacks
Joshua Goldfarb, Director of Product Management at F5,  2/23/2021
News
Cybercrime Groups More Prolific, Focus on Healthcare in 2020
Robert Lemos, Contributing Writer,  2/22/2021
Register for Dark Reading Newsletters
White Papers
Video
Cartoon Contest
Write a Caption, Win an Amazon Gift Card! Click Here
Latest Comment: This comment is waiting for review by our moderators.
Current Issue
2021 Top Enterprise IT Trends
We've identified the key trends that are poised to impact the IT landscape in 2021. Find out why they're important and how they will affect you today!
Flash Poll
Building the SOC of the Future
Building the SOC of the Future
Digital transformation, cloud-focused attacks, and a worldwide pandemic. The past year has changed the way business works and the way security teams operate. There is no going back.
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2021-25284
PUBLISHED: 2021-02-27
An issue was discovered in through SaltStack Salt before 3002.5. salt.modules.cmdmod can log credentials to the info or error log level.
CVE-2021-3144
PUBLISHED: 2021-02-27
In SaltStack Salt before 3002.5, eauth tokens can be used once after expiration. (They might be used to run command against the salt master or minions.)
CVE-2021-3148
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. Sending crafted web requests to the Salt API can result in salt.utils.thin.gen_thin() command injection because of different handling of single versus double quotes. This is related to salt/utils/thin.py.
CVE-2021-3151
PUBLISHED: 2021-02-27
i-doit before 1.16.0 is affected by Stored Cross-Site Scripting (XSS) issues that could allow remote authenticated attackers to inject arbitrary web script or HTML via C__MONITORING__CONFIG__TITLE, SM2__C__MONITORING__CONFIG__TITLE, C__MONITORING__CONFIG__PATH, SM2__C__MONITORING__CONFIG__PATH, C__M...
CVE-2021-3197
PUBLISHED: 2021-02-27
An issue was discovered in SaltStack Salt before 3002.5. The salt-api's ssh client is vulnerable to a shell injection by including ProxyCommand in an argument, or via ssh_options provided in an API request.