A Vulnerability in Fortinet FortiSIEM Could Allow for Remote Code Execution

by jdpoteet | Nov 22, 2023 | Threat Advisories

A Vulnerability in Fortinet FortiSIEM Could Allow for Remote Code Execution

Vulnerability Details

A vulnerability has been discovered in Fortinet FortiSIEM, which could allow for remote code execution. Successful exploitation of this vulnerability could allow for remote code execution in the context of the affected service account. Depending on the privileges associated with the service account an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Service accounts that are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

THREAT INTELLIGENCE:
There are currently no reports of this vulnerability being exploited in the wild.

SYSTEMS AFFECTED:

• Fortinet FortiSIEM versions 4.7 through 5.4

RISK:
Government:

• Large and medium government entities: High
• Small government entities: Medium

Businesses:

• Large and medium business entities: High
• Small business entities: Medium

Home users: Low

TECHNICAL SUMMARY:
A vulnerability has been discovered in Fortinet FortiSIEM, which could allow for remote code execution. Details of the vulnerability is as follows:

Tactic: Initial Access (TA0001):

Technique: Exploit Public-Facing Application (T1190):

• OS command injection vulnerability (CVE-2023-36553)

Successful exploitation of this vulnerability could allow for remote code execution in the context of the affected service account. Depending on the privileges associated with the service account an attacker could then install programs; view, change, or delete data; or create new accounts with full user rights. Service accounts that are configured to have fewer user rights on the system could be less impacted than those who operate with administrative user rights.

RECOMMENDATIONS:
We recommend the following actions be taken:

• Apply appropriate updates provided by Fortinet to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
  • Safeguard 7.1 : Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
  • Safeguard 7.2: Establish and Maintain a Remediation Process: Establish and maintain a risk-based remediation strategy documented in a remediation process, with monthly, or more frequent, reviews.
  • Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
  • Safeguard 7.5 : Perform Automated Vulnerability Scans of Internal Enterprise Assets: Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct both authenticated and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool.
  • Safeguard 7.7: Remediate Detected Vulnerabilities: Remediate detected vulnerabilities in software through processes and tooling on a monthly, or more frequent, basis, based on the remediation process.
  • Safeguard 12.1: Ensure Network Infrastructure is Up-to-Date: Ensure network infrastructure is kept up-to-date. Example implementations include running the latest stable release of software and/or using currently supported network-as-a-service (NaaS) offerings. Review software versions monthly, or more frequently, to verify software support.
  • Safeguard 18.1: Establish and Maintain a Penetration Testing Program: Establish and maintain a penetration testing program appropriate to the size, complexity, and maturity of the enterprise. Penetration testing program characteristics include scope, such as network, web application, Application Programming Interface (API), hosted services, and physical premise controls; frequency; limitations, such as acceptable hours, and excluded attack types; point of contact information; remediation, such as how findings will be routed internally; and retrospective requirements.
  • Safeguard 18.2: Perform Periodic External Penetration Tests: Perform periodic external penetration tests based on program requirements, no less than annually. External penetration testing must include enterprise and environmental reconnaissance to detect exploitable information. Penetration testing requires specialized skills and experience and must be conducted through a qualified party. The testing may be clear box or opaque box.
  • Safeguard 18.3: Remediate Penetration Test Findings: Remediate penetration test findings based on the enterprise’s policy for remediation scope and prioritization.
• Apply the Principle of Least Privilege to all systems and services. Run all software as a non-privileged user (one without administrative privileges) to diminish the effects of a successful attack. (M1026: Privileged Account Management)
  • Safeguard 4.7: Manage Default Accounts on Enterprise Assets and Software:Manage default accounts on enterprise assets and software, such as root, administrator, and other pre-configured vendor accounts. Example implementations can include: disabling default accounts or making them unusable.
  • Safeguard 5.5: Establish and Maintain an Inventory of Service Accounts: Establish and maintain an inventory of service accounts. The inventory, at a minimum, must contain department owner, review date, and purpose. Perform service account reviews to validate that all active accounts are authorized, on a recurring schedule at a minimum quarterly, or more frequently.
• Vulnerability scanning is used to find potentially exploitable software vulnerabilities to remediate them. (M1016: Vulnerability Scanning)
  • Safeguard 16.13: Conduct Application Penetration Testing: Conduct application penetration testing. For critical applications, authenticated penetration testing is better suited to finding business logic vulnerabilities than code scanning and automated security testing. Penetration testing relies on the skill of the tester to manually manipulate an application as an authenticated and unauthenticated user.
• Architect sections of the network to isolate critical systems, functions, or resources. Use physical and logical segmentation to prevent access to potentially sensitive systems and information. Use a DMZ to contain any internet-facing services that should not be exposed from the internal network. Configure separate virtual private cloud (VPC) instances to isolate critical cloud systems. (M1030: Network Segmentation)
  • Safeguard 12.2: Establish and Maintain a Secure Network Architecture: Establish and maintain a secure network architecture. A secure network architecture must address segmentation, least privilege, and availability, at a minimum.
• Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)
  • Safeguard 10.5: Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.

REFERENCES:

Fortiguard:

https://www.fortiguard.com/psirt/FG-IR-23-135

Security Affairs: 
https://securityaffairs.com/154301/security/fortinet-fortisiem-os-command-injection.html

Bleeping Computer:
https://www.bleepingcomputer.com/news/security/fortinet-warns-of-critical-command-injection-bug-in-fortisiem/

CVE:
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-36553
https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-34992

Reptar: A Newly Identified Intel CPU Vulnerability Affects Multi-Tenant Virtualized Environments

by jdpoteet | Nov 21, 2023 | Threat Advisories

Reptar: A Newly Identified Intel CPU Vulnerability Affects Multi-Tenant Virtualized Environments

SUMMARY
Intel issued patches for a high-severity vulnerability named Reptar, which affects Intel desktop, mobile, and server CPUs.

RISK SCORING

CVE-2023-23583               8.8

Vulnerability Details
The vulnerability may allow “escalation of privilege and/or information disclosure and/or denial of service via local access”.  Google (Google Cloud) provided results of their testings of this vulnerability, showing successful exploitation could allow bypassing the CPU’s security boundaries, which was caused by how redundant prefixes are interpreted by the processor.

The impact of this vulnerability is even greater when exploited in a multi-tenant virtualized environment, where a guest machine is attacked and has the capacity to crash the host machine (cascading DoS).  Additionally, the vulnerability poses the extended risk of information disclosure or privilege escalation.

There is no evidence of any active attacks using this vulnerability.

MITIGATIONS
Intel published an updated microcode for all affected processors.

The complete list of Intel CPUs impacted by CVE-2023-23583 is available at:

Affected Processors: Transient Execution Attacks & Related Security… (intel.com)

REFERENCES

• https://www.intel.com/content/www/us/en/developer/topic-technology/software-security-guidance/processors-affected-consolidated-product-cpu-model.html
• https://thehackernews.com/2023/11/reptar-new-intel-cpu-vulnerability.html

Multiple Vulnerabilities in Google Android OS Could Allow for Privilege Escalation

by jdpoteet | Nov 8, 2023 | Threat Advisories

Multiple Vulnerabilities in Google Android OS Could Allow for Privilege Escalation

OVERVIEW
Multiple vulnerabilities have been discovered in Google Android OS, the most severe of which could allow for privilege escalation. Android is an operating system developed by Google for mobile devices, including, but not limited to, smartphones, tablets, and watches. Successful exploitation of the most severe of these vulnerabilities could allow for privilege escalation. Depending on the privileges associated with the exploited component, an attacker could then install programs; view, change, or delete data; or create new accounts with full rights.

THREAT INTELLIGENCE

• There are currently no reports of these vulnerabilities being exploited in the wild.

SYSTEMS AFFECTED

• Android OS patch levels prior to 2023-11-05

RISK
Government:

• Large and medium government entities: High
• Small government entities: Medium

Businesses:

• Large and medium business entities: High
• Small business entities: Medium

Home users: Low

TECHNICAL SUMMARY

Multiple vulnerabilities have been discovered in Google Android OS, the most severe of which could allow for privilege escalation in the context of the affected component. Following the MITRE ATT&CK framework, exploitation of these vulnerabilities can be classified as follows:

Tactic: Privilege Escalation (TA0004):

Technique: Exploitation for Privilege Escalation (T1068):

• Multiple vulnerabilities in Framework that could allow for escalation of privilege. (CVE-2023-40106, CVE-2023-40107, CVE-2023-40109, CVE-2023-40110, CVE-2023-40111, CVE-2023-40114)
• Multiple vulnerabilities in System that could allow for escalation of privilege. (CVE-2023-40100, CVE-2023-40115)

Details of lower-severity vulnerabilities are as follows:

• A vulnerability in System that could allow for information disclosure. (CVE-2023-40113)
• Multiple vulnerabilities in Framework that could allow for information disclosure. (CVE-2023-40105, CVE-2023-40124)
• Multiple vulnerabilities in System that could allow for information disclosure. (CVE-2023-40104, CVE-2023-40112)
• Multiple vulnerabilities in System that could allow for denial of service. (CVE-2023-21103, CVE-2023-21111)
• Multiple vulnerabilities in Project Mainline components. (CVE-2023-40100, CVE-2023-40115)
• A vulnerability in Arm components. (CVE-2023-28469)
• A vulnerability in MediaTek components. (CVE-2023-32832, CVE-2023-32834, CVE-2023-32835, CVE-2023-32836, CVE-2023-32837, CVE-2023-20702)
• Multiple vulnerabilities in Qualcomm components. (CVE-2023-33031, CVE-2023-33055, CVE-2023-33059, CVE-2023-33074)
• Multiple vulnerabilities in Qualcomm closed-source components. (CVE-2023-21671, CVE-2023-22388, CVE-2023-28574, CVE-2023-33045, CVE-2023-24852, CVE-2023-28545, CVE-2023-28556, CVE-2023-33047, CVE-2023-33048, CVE-2023-33056, CVE-2023-33061)

Successful exploitation of the most severe of these vulnerabilities could allow for privilege escalation. Depending on the privileges associated with the exploited component, an attacker could then install programs; view, change, or delete data; or create new accounts with full rights.

RECOMMENDATIONS
We recommend the following actions be taken:

• Apply appropriate updates and patches provided by Google to vulnerable systems immediately after appropriate testing. (M1051: Update Software)
  • Safeguard 7.1: Establish and Maintain a Vulnerability Management Process: Establish and maintain a documented vulnerability management process for enterprise assets. Review and update documentation annually, or when significant enterprise changes occur that could impact this Safeguard.
  • Safeguard 7.4: Perform Automated Application Patch Management: Perform application updates on enterprise assets through automated patch management on a monthly, or more frequent, basis.
  • Safeguard 7.5: Perform Automated Vulnerability Scans of Internal Enterprise Assets: Perform automated vulnerability scans of internal enterprise assets on a quarterly, or more frequent, basis. Conduct both authenticated and unauthenticated scans, using a SCAP-compliant vulnerability scanning tool.
• Use capabilities to detect and block conditions that may lead to or be indicative of a software exploit occurring. (M1050: Exploit Protection)

• • Safeguard 10.5:  Enable Anti-Exploitation Features: Enable anti-exploitation features on enterprise assets and software, where possible, such as Microsoft® Data Execution Prevention (DEP), Windows® Defender Exploit Guard (WDEG), or Apple® System Integrity Protection (SIP) and Gatekeeper™.

• Restrict execution of code to a virtual environment on or in transit to an endpoint system. (M1048: Application Isolation and Sandboxing)
  • Safeguard 16.8: Separate Production and Non-Production Systems: Maintain separate environments for production and non-production systems.

REFERENCES

Google:

• https://source.android.com/docs/security/bulletin/2023-11-01#2023-11-05-security-patch-level-vulnerability-details

CVE:

• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-20702
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21103
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21111
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-21671
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-22388
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-24852
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-28469
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-28545
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-28556
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-28574
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32832
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32834
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32835
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32836
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32837
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33031
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33045
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33047
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33048
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33055
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33056
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33059
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33061
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-33074
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40100
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40100
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40104
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40105
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40106
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40107
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40109
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40110
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40111
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40112
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40113
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40114
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40115
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40115
• https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-40124