Cloud technology giant ServiceNow appears to have notified some of its enterprise customers that a software bug on its platform was allowing anyone on the internet to access their data.<\/p>\n
A knowledge base article<\/a>, which ServiceNow has hidden behind a login wall but has been shared on Reddit<\/a>, says the company on June 5 patched some customer instances to fix a bug that had allowed unauthenticated users to \u201cgain greater access\u201d to ServiceNow-hosted data than intended.<\/p>\n The bug allowed potentially anyone to obtain data stored in customer instances without requiring credentials, such as a password.\u00a0<\/p>\n It\u2019s not clear who had improper access to ServiceNow customers, what data was accessed or taken, or if any group was involved. Given that the security incident appears to stem from a data-exposing bug, it\u2019s unclear if customers could have protected themselves from improper access.<\/p>\n ServiceNow is a cloud computing giant that allows thousands of its enterprise customers to automate their internal business processes. Companies use the tech giant\u2019s platform to build workflows that connect to various apps and databases, such as IT and HR systems, which can be used to automatically handle repeat tasks, like onboarding staff, resolving tech support tickets, and for chatbots.<\/p>\n As such, companies like ServiceNow are high-value targets for hackers thanks to the amount of sensitive data that they store, such as customer support tickets, which can include passwords, keys and credentials.<\/p>\n ServiceNow said the issue relates to customer instances running its Australia releases<\/a>, but several people on Reddit<\/a> say they have identified evidence of external access to ServiceNow instances running other versions of its software. Network defenders shared an IP address<\/a>, 51.159.98.241, said to be an indicator of potential compromise if found in a customer\u2019s logs.<\/p>\n A spokesperson for ServiceNow did not immediately return TechCrunch\u2019s email requesting comment and seeking answers on how many customers are affected, or how long the bug had exposed the data.<\/p>\n Corrected the seventh paragraph to update references to the Australia releases, unrelated to geography.<\/p>\n