New Delhi: OpenAI, the creator of ChatGPT, has admitted that some customers` cost data might have been uncovered earlier this week when it took ChatGPT offline owing to a bug. According to the corporate, the Microsoft-owned firm took ChatGPT offline attributable to a bug in an open-source library which allowed some customers to see titles from one other lively person`s chat historical past.
“It was also possible that the first message of a newly-created conversation was visible in someone else`s chat history if both users were active around the same time,” stated the corporate. The bug has been patched and ChatGPT service and its chat historical past characteristic, apart from just a few hours of historical past, have been restored.
However, upon deeper investigation, OpenAI found that the identical bug might have triggered the unintentional visibility of “payment-related information of 1.2 per cent of the ChatGPT Plus subscribers who were active during a specific nine-hour window”.
“In the hours before we took ChatGPT offline, it was possible for some users to see another active user`s first and last name, email address, payment address, the last four digits (only) of a credit card number, and credit card expiration date. Full credit card numbers were not exposed at any time,” the corporate revealed. Due to the bug, some subscription affirmation emails generated throughout that window have been despatched to the fallacious customers. These emails contained the final 4 digits of one other customers` bank card quantity, however full bank card numbers didn’t seem.
“It`s possible that a small number of subscription confirmation emails might have been incorrectly addressed prior to March 20, although we have not confirmed any instances of this,” OpenAI additional stated. The firm stated it has reached out to inform affected customers that their cost data might have been uncovered.
“We are confident that there is no ongoing risk to users` data,” it added, apologising once more to customers and to your entire ChatGPT group. The bug was found within the Redis shopper open-source library known as “redis-py”.
