Wednesday, December 18, 2024
HomeCyber Security NewsServiceNow Misconfigurations Lead to Leak of Sensitive Data

ServiceNow Misconfigurations Lead to Leak of Sensitive Data

Published on

SIEM as a Service

ServiceNow has been alerted to a potential misconfiguration concern that might impact the security of its platform. The company is actively addressing the issue and working towards a resolution.

The issue involves Access Control Lists (ACLs), which are used to control access to tables and columns on the platform. 

If an ACL is empty or does not have any roles, conditions, or scripts, it could allow unauthorized users, including guests, to access some resources.

- Advertisement - SIEM as a Service

ServiceNow has found that unauthenticated users have limited access to the platform and can only access some authorized pages. 

However, some public portal widgets, such as SimpleListWidget, can query data from the system. ServiceNow advises customers to follow these steps to check and fix their ACLs:

Check ACL Configurations

Customers should find ACLs that do not have any roles, conditions, or scripts.

If they do not want unauthenticated users to access those tables, they should add `gs.isLoggedIn()` to the script section of the ACLs. This will prevent unauthenticated users from accessing those tables through public portal widgets.

General Security Measures

ServiceNow recommends a thorough review of all ACLs, especially those that are empty or have the role “Public,” to make sure they match the business and security requirements.

Customers should also review their public widgets and disable the “Public” flag if they do not need them.

Customers should use IP Address Access Control to restrict access to their instances to only trusted IP addresses. Alternatively, they can use Adaptive Authentication policies to apply more fine-grained authentication control, allowing mobile access but limiting access to specific IP ranges and subnets.

Explicit Roles Plugin

Instances that use the Explicit Roles plugin are not affected by this issue. ServiceNow advises customers who use this plugin to check their ACLs that have the “public” role and review their User Criteria configurations.

ServiceNow stresses the importance of taking proactive security measures and urges customers to follow these steps to protect their instances.

The guidelines for assessing User Criteria can be located at KB1123580.

ServiceNow will continue to investigate the issue and provide updates and guidance as needed. Stay tuned for more information on this issue.

Protect yourself from vulnerabilities using Patch Manager Plus to patch over 850 third-party applications quickly. Try a free trial to ensure 100% security.

Gurubaran
Gurubaran
Gurubaran is a co-founder of Cyber Security News and GBHackers On Security. He has 10+ years of experience as a Security Consultant, Editor, and Analyst in cybersecurity, technology, and communications.

Latest articles

New VIPKeyLogger Via Weaponized Office Documenrs Steals Login Credentials

The VIPKeyLogger infostealer, exhibiting similarities to the Snake Keylogger, is actively circulating through phishing...

INTERPOL Urges to End ‘Pig Butchering’ & Replaces With “Romance Baiting”

INTERPOL has called for the term "romance baiting" to replace "pig butchering," a phrase...

New I2PRAT Malware Using encrypted peer-to-peer communication to Evade Detections

Cybersecurity experts are sounding the alarm over a new strain of malware dubbed "I2PRAT,"...

Earth Koshchei Employs RDP Relay, Rogue RDP server in Server Attacks

 A new cyber campaign by the advanced persistent threat (APT) group Earth Koshchei has...

API Security Webinar

72 Hours to Audit-Ready API Security

APIs present a unique challenge in this landscape, as risk assessment and mitigation are often hindered by incomplete API inventories and insufficient documentation.

Join Vivek Gopalan, VP of Products at Indusface, in this insightful webinar as he unveils a practical framework for discovering, assessing, and addressing open API vulnerabilities within just 72 hours.

Discussion points

API Discovery: Techniques to identify and map your public APIs comprehensively.
Vulnerability Scanning: Best practices for API vulnerability analysis and penetration testing.
Clean Reporting: Steps to generate a clean, audit-ready vulnerability report within 72 hours.

More like this

New VIPKeyLogger Via Weaponized Office Documenrs Steals Login Credentials

The VIPKeyLogger infostealer, exhibiting similarities to the Snake Keylogger, is actively circulating through phishing...

INTERPOL Urges to End ‘Pig Butchering’ & Replaces With “Romance Baiting”

INTERPOL has called for the term "romance baiting" to replace "pig butchering," a phrase...

New I2PRAT Malware Using encrypted peer-to-peer communication to Evade Detections

Cybersecurity experts are sounding the alarm over a new strain of malware dubbed "I2PRAT,"...