The National Initiative for Cybersecurity Education (NICE) is continuing to refine and clarify the Workforce Framework for Cybersecurity (NICE Framework) as a fundamental reference resource that is agile, flexible, modular, and interoperable. As such, a review of the NICE Framework data – Competency Areas, Work Roles, and Task, Knowledge, and Skill (TKS) statements – is in progress and we are pleased to announce that the initial review of Knowledge and Skill statements is ready for your feedback! 

Updated Knowledge and Skill statements are here! 
Draft updated Knowledge statements and Skill statements are available for public review and comment. Adjustments address: 

• Alignment with TKS Authoring Guide principles
• Unnecessary redundancies or duplicates
• Inconsistent and unclear language

As a result of these adjustments, the TKS building blocks are more measurable, meaningful, and useful. Please note that this process will be an iterative one, and the NICE Program Office will conduct a full review of the updated Knowledge and Skill statements and the refactored Ability statements (previously released for comment) as a whole following comment adjudication.

We want to hear from you!
Comments on the updated Knowledge and Skill statements should be submitted by email to NICEFramework@nist.gov by 11:59pm ET on June 3, 2022.

 This FLASH is part of a
series of FBI reports to disseminate known indicators of compromise (IOCs)
and tactics, techniques and procedures (TTPs) associated with ransomware
variants identified through FBI investigations. As of March 2022, BlackCat/ALPHV
ransomware as a service (RaaS) had compromised at least 60 entities
worldwide and is the first ransomware group to do so successfully using
RUST, considered to be a more secure programming language that offers
improved performance and reliable concurrent processing.
BlackCat-affiliated threat actors typically request ransom payments of
several million dollars in Bitcoin and Monero but have accepted ransom
payments below the initial ransom demand amount. Many of the developers
and money launderers for BlackCat/ALPHV are linked
to Darkside/Blackmatter, indicating they have extensive networks and
experience with ransomware operations.

Details 

to read the full details go here

 

The National Cybersecurity Center of Excellence (NCCoE) announces
the release of three related publications on trusted cloud and hardware-enabled
security. The foundation of any data center or edge computing security strategy
should be securing the platform on which data and workloads will be executed
and accessed. The physical platform represents the first layer for any layered
security approach and provides the initial protections to help ensure that
higher-layer security controls can be trusted.

Trusted Cloud: Security Practice Guide for VMware Hybrid Cloud Infrastructure as a Service (IaaS) Environments (NIST SP 1800-19)	NIST Special Publication (SP) 1800-19 presents an example of a trusted hybrid cloud solution that demonstrates how trusted compute pools leveraging hardware roots of trust can provide the necessary security capabilities for cloud workloads in addition to protecting the virtualization and application layers. View the document.
Each of the reports below, NISTIR 8320B and NISTIR 8320C, are intended to be used as a blueprint or template that the general security community can use as example proof of concept implementations.
Hardware-Enabled Security: Policy-Based Governance in Trusted Container Platforms (NISTIR 8320B)	NISTIR 8320B explains an approach based on hardware-enabled security techniques and technologies for safeguarding container deployments in multi-tenant cloud environments. View the document.
Hardware-Enabled Security: Machine Identity Management and Protection (NISTIR 8320C)	Draft NISTIR 8320C presents an approach for overcoming security challenges associated with creating, managing, and protecting machine identities, such as cryptographic keys, throughout their lifecycle. View the document.

We Want to Hear from You!

Review the draft NISTIR 8320C and submit comments online on or before
June 6, 2022. You can also contact us at hwsec@nist.gov.
We value and welcome your input and look forward to your comments.

ESET researchers have discovered and analyzed three vulnerabilities affecting various Lenovo consumer laptop models. The first two of these vulnerabilities – CVE-2021-3971, CVE-2021-3972 – affect UEFI firmware drivers originally meant to be used only during the manufacturing process of Lenovo consumer notebooks. Unfortunately, they were mistakenly included also in the production BIOS images without being properly deactivated. These affected firmware drivers can be activated by attacker to directly disable SPI flash protections (BIOS Control Register bits and Protected Range registers) or the UEFI Secure Boot feature from a privileged user-mode process during OS runtime. It means that exploitation of these vulnerabilities would allow attackers to deploy and successfully execute SPI flash or ESP implants, like LoJax or our latest UEFI malware discovery ESPecter, on the affected devices.

To understand how we were able to find these vulnerabilities, consider the firmware drivers affected by CVE‑2021-3971. These drivers immediately caught our attention by their very unfortunate (but surprisingly honest) names: SecureBackDoor and SecureBackDoorPeim. After some initial analysis, we discovered other Lenovo drivers sharing a few common characteristics with the SecureBackDoor* drivers: ChgBootDxeHook and ChgBootSmm. As it turned out, their functionality was even more interesting and could be abused to disable UEFI Secure Boot (CVE-2021-3972).

In addition, while investigating above mentioned vulnerable drivers, we discovered the third vulnerability: SMM memory corruption inside the SW SMI handler function (CVE-2021-3970). This vulnerability allows arbitrary read/write from/into SMRAM, which can lead to the execution of malicious code with SMM privileges and potentially lead to the deployment of an SPI flash implant.

We reported all discovered vulnerabilities to Lenovo on October 11th, 2021. Altogether, the list of affected devices contains more than one hundred different consumer laptop models with millions of users worldwide, from affordable models like Ideapad-3 to more advanced ones like Legion 5 Pro-16ACH6 H or Yoga Slim 9-14ITL05. The full list of affected models with active development support is published in the Lenovo Advisory.

In addition to the models listed in the advisory, several other devices we reported to Lenovo are also affected, but won’t be fixed due to them reaching End Of Development Support (EODS). This includes devices where we spotted reported vulnerabilities for the first time: Ideapad 330-15IGM and Ideapad 110-15IGR. The list of such EODS devices that we have been able to identify will be available in ESET’s vulnerability disclosures repository.

Lenovo confirmed the vulnerabilities on November 17th, 2021, and assigned them the following CVEs:

• CVE-2021-3970 LenovoVariableSmm – SMM arbitrary read/write
• CVE-2021-3971 SecureBackDoor – disable SPI flash protections
• CVE-2021-3972 ChgBootDxeHook – disable UEFI Secure Boot

Highlights:

·       
Check Point Research discovered vulnerabilities in the ALAC
format that could have led an attacker to remotely get access to its media and
audio conversations

·       
MediaTek and Qualcomm, the two largest mobile chipset manufacturers
in the world, used the ALAC audio coding in their widely distributed mobile
handsets, putting millions of Android users’ privacy at risk

·       
Research, dubbed “ALHACK” finds Two thirds of
all smartphones sold in 2021 are vulnerable

·       
Qualcomm and MediaTek acknowledged the vulnerabilities flagged
by CPR, putting patches and fixes in response

Background

The
Apple Lossless Audio Codec (ALAC), also known as Apple Lossless, is an audio
coding format, developed by Apple Inc. and first introduced in 2004 for
lossless data compression of digital music.

In
late 2011 Apple made the codec open source. Since then, the ALAC format has
been embedded in many non-Apple audio playback devices and programs, including
Android-based smartphones, Linux and Windows media players and converters.

Since
then Apple has been updating the proprietary version of the decoder several
times, fixing and patching security issues, but the shared code has not been
patched since 2011. Many third-party vendors use the Apple-supplied code as the
basis for their own ALAC implementations, and it’s fair to assume that many of
them do not maintain the external code.

Check
Point Research has discovered that Qualcomm and MediaTek, two of the largest
mobile chipset makers in the world, ported the vulnerable ALAC code into their
audio decoders, which are used in more than half of all smartphones worldwide.
According to IDC, 48.1% of all Android phones sold in the
US are powered by MediaTek as of Q4 2021, while Qualcomm currently holds 47% of
the market.

What did we find and
what is the potential threat?

The
ALAC issues our researchers found could be used by an attacker for remote code
execution attack (RCE) on a mobile device through a malformed audio file. RCE
attacks allow an attacker to remotely execute malicious code on a computer. The
impact of an RCE vulnerability can range from malware execution to an attacker
gaining control over a user’s multimedia data, including streaming from a
compromised machine’s camera.

In
addition, an unprivileged Android app could use these vulnerabilities to
escalate its privileges and gain access to media data and user conversations.

Responsible disclosure

Check
Point Research responsibly disclosed the information to MediaTek and Qualcomm
and worked closely in collaboration with both vendors to make sure these
vulnerabilities were fixed.

MediaTek
assigned CVE-2021-0674 and CVE-2021-0675 to the ALAC issues. The
vulnerabilities were already fixed and published in the
December 2021 MediaTek Security Bulletin. Qualcomm released the patch for
CVE-2021-30351 in the December 2021 Qualcomm Security Bulletin.

 Source of the article found here

 Summary

 

This Multi-State Infrastructure Information Sharing and Analysis Center (MS-ISAC) Advisory is being provided to assist agencies and organizations in guarding against the persistent malicious actions of cybercriminals. Even though the services provided by the MS-ISAC are only available to the public sector, all private sector organizations are encouraged to review this Advisory and implement appropriate mitigation measures.

 

Summary The MS-ISAC received notice from a trusted third-party regarding subdomains of ru[.]com using the names of US states. Although many of them are not currently active, these domains could be used for phishing campaigns or other malicious activity like malspam. The domains follow a consistent template with using standard state names (no acronyms, spacing, or hyphens) in the format <state>[.]ru[.]com. For example:

 

California[.]ru[.]com NewYork[.]ru[.]com NorthDakota[.]ru[.]com Ohio[.]ru[.]com

 

This information is being provided for situational awareness. The MS-ISAC recommends blocking the domain at your web filter, on any edge devices, and in your spam filtering solution. If your organization utilizes the MS-ISAC Malicious Domain Blocking and Reporting (MDBR) Service, all of the domains have been added. While some of these domains are currently up for sale, the domain could become active at any time.