Tuesday, October 6, 2020

FAA Sends Two Drone Final Rules to OMB

Yesterday the OMB’s Office of Information and Regulatory Affairs (OIRA) announced that it had received two final rules from the DOT’s Federal Aviation Administration (FAA) for review. Both rulemakings address unmanned aircraft operations. The rulemakings address remote identification of drones and operations over people.

Remote Identification

The first rulemaking concerns “Remote Identification of Unmanned Aircraft Systems”. The notice of proposed rulemaking (NPRM) for this rule was published in December of last year. According to the Spring 2020 Unified Agenda listing for this action:

“This action would require the remote identification of unmanned aircraft systems. The remote identification of unmanned aircraft systems in the airspace of the United States would address safety, national security, and law enforcement concerns regarding the further integration of these aircraft into the airspace of the United States while also enabling greater operational capabilities.”

Operating Over People

The second rulemaking concerns “Operations of Small Unmanned Aircraft Over People”. The NPRM for this rule was published in February of 2019. . According to the Spring 2020 Unified Agenda listing for this action:

“This rulemaking would address the performance-based standards and means-of-compliance for operation of small unmanned aircraft systems (UAS) over people not directly participating in the operation or not under a covered structure or inside a stationary vehicle that can provide reasonable protection from a falling small unmanned aircraft. This rule would provide relief from certain operational restrictions implemented in the Operation and Certification of Small Unmanned Aircraft Systems final rule (RIN 2120-AJ60).”

Saturday, October 3, 2020

Update on CISA Chemical Security Seminars – 10-3-20

This week the Cybersecurity and Infrastructure Security Agency updated their Chemical Security Summit web page, providing additional information on the chemical security seminars that will be taking the place of this year’s COVID-19 canceled Chemical Security Summit. Seminars will be held on December 2nd, 9th, and 16th. A brief agenda outline has been included.

The topics that will be addressed include:

• The state of chemical security—Updates for the Chemical Facility Anti-Terrorism Standards (CFATS) program and ongoing nonregulatory chemical security efforts

• A demo of the CFATS Personnel Surety Program application

• A deep dive into the 18 CFATS Risk-Based Performance Standards (RBPS) and best practices

• A chemical threat briefing

• Managing chemical security during natural disasters: hurricanes, wildfires, floods, and pandemics

• Challenges encountered with chemical security during the COVID-19 pandemic

• Growing a global culture of chemical security

• The convergence of cyber and physical security

Public ICS Disclosures – Week of 9-26-20

This week we have ten vendor disclosures for products from WAGO (3), IBM, Bosch, B&R Automation (2), Moxa, BD, and Philips.

WAGO Advisories

CERT-VDE published an advisory describing an improper authentication and authorization vulnerability in the WAGO 750-8XX series PLCs. The vulnerability was reported by Maxim Rupp. WAGO has new firmware versions that mitigate the vulnerability. There is no indication that Maxim has been provided an opportunity to verify the efficacy of the fix.

CERT-VDE published an advisory describing an improper authentication and access control vulnerability in the WAGO 750-36X and WAGO 750-8XX series PLCs. The vulnerability was reported by Maxim Rupp. WAGO has new firmware versions that mitigate the vulnerability. There is no indication that Maxim has been provided an opportunity to verify the efficacy of the fix.

CERT-VDE published an advisory describing an improper neutralization of input during web page generation vulnerability in the Web-UI for WAGO 750-88X and WAGO 750-89X series PLCs. This vulnerability was reported by Secuninja. WAGO has new firmware versions that mitigate the vulnerability. There is no indication that Secuninja has been provided an opportunity to verify the efficacy of the fix.

IBM Advisory

IBM published an advisory describing an authentication bypass vulnerability in their Maximo Asset Management product. The vulnerability is being self-reported. IBM has updates that mitigate the vulnerability.

Bosch Advisory

Bosch published an advisory describing three vulnerabilities in their PRAESIDEO Network Controller and the PRAESENSA System Controller products. The vulnerabilities were reported by Gjoko Krstic of Applied Risk. Bosch has software updates for the supported products that mitigate the vulnerabilities. There is no indication that Krstic has been provided an opportunity to verify the efficacy of the fix.

The three reported vulnerabilities are:

• Cross-site scripting - CVE-2020-6777,

• Cross-site request forgery - CVE-2020-6776, and

• Nonce reuse attack - CVE-2020-15688

NOTE: The last is a third-party vulnerability (GoAhead web server).

B&R Advisories

B&R published an advisory describing four vulnerabilities in their GateManager product. These vulnerabilities were reported by NCCIC-ICS on July 28th as being for the Secomea GateManager.

B&R published an advisory describing six vulnerabilities in their SiteManager and GateManager procucts. These vulnerabilities were reported by NCCIC-ICS last Tuesday, but the B&R advisory was not available when I published my blog post. It is not clear if the Secomea versions of these products are also affected by these vulnerabilities.

Moxa Advisory

Moxa published an advisory describing a device information leak vulnerability in their EDR-810 Series Industrial Secure Routers. The vulnerability was reported by the National Security Agency (yep, that is what the advisory says). Moxa has provided generic workarounds to mitigate the vulnerability.

BD Advisory

BD published an advisory describing a remote code execution vulnerability (CVE-2020-1147) in a third-party component (Microsoft) of a long list of their products. BD is working on testing and validation of the Microsoft patch.

Philips Advisory

Philips published an advisory describing a privilege elevation vulnerability (CVE-220-1472) in a third-party component (Microsoft) of an undisclosed number of Philips products. No mitigation information has been provided.

Friday, October 2, 2020

Bills Introduced – 10-1-20

Yesterday, with both the House and Senate in session (an unusual October session in an election year), there were 67 bills introduced. One of those bills will receive additional coverage in this blog:

S 4795 A bill to require the Secretary of Energy to establish a voluntary Cyber Sense program to test the cybersecurity of products and technologies intended for use in the bulk-power system, and for other purposes. Sen. Rosen, Jacky [D-NV] 

It is unusual for this bill to be introduced this late in the session when the House just passed their version of the bill this week. It will be interesting to see what the differences are between this bill and HR 360.

Thursday, October 1, 2020

1 Update Published – 10-1-20

 Today the CISC NCCIC-ICS published a control system security update for the CodeMeter vulnerabilities from Wibu-Systems.

CodeMeter Update

This update provides additional information that was originally published on September 8th, 2020 and most recently updated on September 17th, 2020. The new information includes links to new affected vendor disclosures from:

ABB,

Bosch, and

COPA-DATA

NOTE: The ABB link is to their Alerts and Notifications page. There are currently four CodeMeter advisories listed on that page. One is a generic advisory and the other three are product specific advisories. I briefly described this in a blog post on September 12th. I briefly discussed the Bosch advisory on September 26th

HR 360 and Congresscritters

While there was no opposition to the four DOE cybersecurity bills passed Tuesday in the House, it is worthwhile to read the debate on these bills. I would specifically like to call your attention to the debate on HR 360, the Cyber Sense Act.

As with most bills considered in the House under the suspension of the rules process, there were no opposing voices heard on this bill. Most of the ‘debate’ is praise for the bills authors and the committee leadership for moving the bill forward. Every once-in-a-while you will hear a congress person talk about the provisions of the bill under consideration. For HR 360, Rep Walden (R,OR) was one such voice.

Amongst other positive comments about the bill, Walden said:

“The bill also was amended to make clear these efforts of the Department of Energy would include, as appropriate, other relevant Federal agencies like the Department of Homeland Security.”

Unfortunately, he was mistaken. According to the Committee Report on the bill from the House Energy and Commerce Committee (pg 5):

“On July 17, 2019, the full Committee on Energy and Commerce met in open markup session, pursuant to notice, to consider H.R. 360. No amendments were offered at full Committee. Subsequently, the Committee agreed to a motion by Mr. Pallone, Chairman, to order the bill H.R. 360 reported favorably to the House, without amendment [emphasis added], by a voice vote, a quorum being present.”

Furthermore, the language included in the Congressional Record is the same language as was adopted by the Committee.

Okay, to err is human so even congresscritters should be forgiven for their human frailties. And to be fair, perhaps he confused HR 360 with one of the other DOE cybersecurity bills being considered in the House on Tuesday. But, no, none of those bills had language added that sounds anything like that described by Walden. In fact, sharp eyed readers of this blog might recall that such language was actually removed from HR 359, as I reported on Monday.

So, does this mean that Walden is a bad person? Of course not; not even a bad congresscritter. People misremember things all of the time. It just means that when you read what a congresscritter tells you about a bill, you have to verify what they say. Read the bill yourself. Remember that congresscritters probably do not have the time to do that for each bill they consider in the course of their job.

HR 5760 Passed in House – Grid Security Research

I missed this in yesterday’s post on DOE legislation passed in the House, but on Tuesday the House passed HR 5760, the Grid Security Research and Development Act. It passed by a voice vote under the suspension of the rules process. There was limited debate and no one spoke in opposition to the bill.

Again, reiterating what I said yesterday, this bill will only be considered in the Senate if it is taken up under their unanimous consent process. Because of COVID-19, the election, and the general inability of the current Senate to consider much of anything beyond judicial nominations, it is unlikely that this bill will be considered in the Senate.

 
/* Use this with templates/template-twocol.html */