Jump to content

Search the Community

Showing results for tags 'security breach'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Site Related
    • News & Updates
    • Site / Forum Feedback
    • Member Introduction
  • News
    • General News
    • FileSharing News
    • Mobile News
    • Software News
    • Security & Privacy News
    • Technology News
  • Downloads
    • nsane.down
  • General Discussions & Support
    • Filesharing Chat
    • Security & Privacy Center
    • Software Chat
    • Mobile Mania
    • Technology Talk
    • Entertainment Exchange
    • Guides & Tutorials
  • Off-Topic Chat
    • The Chat Bar
    • Jokes & Funny Stuff
    • Polling Station

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Found 6 results

  1. Five servers storing customer support analytics were accidentally exposed online in December 2019. Microsoft disclosed today a security breach that took place last month in December 2019. In a blog post today, the OS maker said that an internal customer support database that was storing anonymized user analytics was accidentally exposed online without proper protections between December 5 and December 31. The database was spotted and reported to Microsoft by Bob Diachenko, a security researcher with Security Discovery. The leaky customer support database consisted of a cluster of five Elasticsearch servers, a technology used to simplify search operations, Diachenko told ZDNet today. All five servers stored the same data, appearing to be mirrors of each other. Diachenko said Microsoft secured the exposed database on the same day he reported the issue to the OS maker, despite being New Year's Eve. "I have been in touch with the Microsoft team helping and supporting them to properly investigate it," Diachenko told ZDNet. The servers contained roughly 250 million entries. Microsoft says that most of the records didn't contain any personal user information. "As part of Microsoft's standard operating procedures, data stored in the support case analytics database is redacted using automated tools to remove personal information," Microsoft said. However, in cases where users filed customer support requests using non-standard formatted data such as ("name surname @ emaildomain com" instead of "[email protected]") the data was not detected and redacted, and remained in the exposed database. For these cases, Microsoft said it began notifying impacted customers today, although it also added that it "found no malicious use" of the data. Microsoft blamed the accidental server exposure on misconfigured Azure security rules it deployed on December 5, which it now fixed. Following the leak, Microsoft says it is now: Auditing the established network security rules for internal resources. Expanding the scope of the mechanisms that detect security rule misconfigurations. Adding additional alerting to service teams when security rule misconfigurations are detected. Implementing additional redaction automation. Source
  2. The US branch of telecommunications giant T-Mobile disclosed a security breach today that impacted a small number of customers of its prepaid service. The company said its cybersecurity team "discovered and shut down malicious, unauthorized access to some information related to your T-Mobile prepaid wireless account." Exposed data included details such as customer names, billing addresses, phone numbers, account numbers, rate plans, and plan features. T-Mobile said hackers didn't access any sensitive information such as passwords, financial information, or social security numbers. The telco said it notified law enforcement of the incident, and is now reaching out to customers. Impacted users should have received an SMS today, but if users have changed numbers or have switched to other provides and would like to find out if they've been impacted, they can contact and ask the company for confirmation at [email protected] T-Mobile said all impacted users should change account passwords and PIN codes. Additional details are available in a T-Mobile support page. T-Mobile joins Sprint as the second major US telco to disclose a security breach this year. In July, Sprint said hackers accessed some customer data via the Samsung official website. Earlier this year, in May, Sprint also disclosed another breach when it said hackers used Boost phone numbers and Boost.com PIN codes to access users' Sprint accounts. T-Mobile did not return a request for comment seeking additional details about the incident. Source
  3. Foxit Software said hackers breached website accounts and stole user information. Foxit Software, the company behind the Foxit PDF reader app, said today that hackers breached its servers and have made off with some user information. ZDNet learned of the breach from a Foxit customer who shared a copy of the email the company is sending out to affected users, asking them to choose new passwords when logging in the next time. According to this email, the security breach impacted the company's website, and, namely, information stored in the My Account section. Foxit web accounts are how the company manages its existing customers and is where users can access trial software, download purchased products, and access order histories. Foxit said hackers managed to access MyAccount data such as email addresses, passwords, real names, phone numbers, company names, and IP addresses from which users logged into their accounts. Due to the presence of IP addresses in the data hackers managed to access, this is believed to be a breach of Foxit's backend infrastructure, rather than a credential stuffing attack. A Foxit spokesperson could not be reached for additional clarification. Were the passwords hashed or in plaintext? The biggest mystery is if Foxit had protected customer passwords through a process called hashing and salting. Hashing and salting a password string prevents an attacker from being able to read it in plaintext. The email sent to customers and a security advisory posted on the Foxit Software website did not mention if passwords were either hashed and salted. The software maker said it invalidated all passwords for customers who it believed were impacted by the security breach. However, if the passwords were available in cleartext, then attackers can use them to gain access to users' accounts on other websites if users made the mistake of reusing passwords. Foxit also didn't date the security incident, and it's currently unknown if the breach occurred this week, last month, or in previous years. If this is an old breach that has only been recently discovered, than hackers might have had a huge head start in abusing the stolen data. The company did say, however, that hackers didn't access any financial information. It also said it's working with a forensic firm to investigate further, and that it notified law enforcement and data protection authorities. Foxit Software should not be confused with Fox-IT, a cyber-security firm with a similar name, which had its own cyber-security incident in December 2017. Source
  4. Equifax revealed its earnings release related to the security breach suffered in 2017, the incident has cost about $1.4 billion plus legal fees. Equifax revealed this week its earnings release related to the security breach suffered by the credit bureau back in 2017, the incident has cost about $1.4 billion plus legal fees. In 2017 Equifax confirmed it has suffered a massive data breach, cyber criminals stole sensitive personal records of 145 million belonging to US citizens and hundreds of thousands Canada and in the UK. Attackers exploited the CVE-2017-5638 Apache Struts vulnerability. The vulnerability affects the Jakarta Multipart parser upload function in Apache and could be exploited by an attacker to make a maliciously crafted request to an Apache web server. The vulnerability was fixed back in March 2017, but the company did not update its systems, the thesis was also reported by an Apache spokeswoman to the Reuters agency. Compromised records included names, social security numbers, birth dates, home addresses, credit-score dispute forms, and for some users also the credit card numbers and driver license numbers. In March 2018, experts argued the Equifax hack is worse than previously thought, according to documents provided by Equifax to the US Senate Banking Committee the attackers also stole taxpayer identification numbers, phone numbers, email addresses, and credit card expiry dates belonging to some Equifax customers. A few weeks later the results of the forensic investigation revealed additional 2.4 Million identities were involved in the security incident. Chief Executive Mark Begor confirmed that Equifax reached settlement agreements recently with some of the class action lawsuits and government investigators. “This is a positive step forward for Equifax, as we work to put the 2017 cybersecurity event behind us,” he explained. According to Begor, the settlement terms include the creation of a single “consumer redress fund” to respond and consolidate redress requests. “There are still many other lawsuits outstanding.” reported the website Wabe.org. “The company has said hundreds of suits were filed against it since the breach, including more than 2,500 individual consumer plaintiffs, international and domestic class action suits, shareholder litigation and government lawsuits from states and cities.” In June 2018, Equifax agreed to the Consent Order from some state banking regulators, many governmental agencies and officials are still investigating the breach. “The company said earlier this year that the Consumer Financial Protection Bureau and Federal Trade Commission had told Equifax the agencies do “intend to seek injunctive relief damages and, with respect to the CFPB, civil money penalties against us based on allegations related to the 2017 cybersecurity incident.”” continues the Wabe site. Expert believe that Equifax must be punished with exemplary penalties that have to incentivize the credit bureaus to protect consumer data. “Equifax still hasn’t paid a price two years after losing the financial DNA of 150 million Americans,” said Mike Lit, a national campaign director at the consumer advocate, U.S. Public Interest Research Group. “That’s why we need strong oversight and meaningful financial penalties to incentivize the credit bureaus to protect our data.” Source
  5. Company behind Indiana Pacers and Indiana Fever said hackers breached employee accounts, stole personal data. Pacers Sports & Entertainment (PSE), the legal entity behind the Indiana Pacers and the Indiana Fever NBA and WNBA basketball teams, respectively, announced a security breach on Friday during which hackers gained access to sensitive user information. In a press release published yesterday, the company blamed the breach on phishing campaign during which hackers managed to gain access to several PSE employee accounts. It said hackers had access to these accounts between October 15, 2018, and December 4, 2018. PSE is notifying customers now, but the company said it learned of the breach way back last year, on November 16, leaving many to ask themselves --what took so long? "After a thorough review of these email accounts, PSE determined that a limited number of personal records were present in the affected emails," the company said. Exposed information ranges wildly, and PSE said it might include name, address, date of birth, passport number, medical and/or health insurance information, driver's license/state identification number, account number, credit/debit card number, digital signature, username and password, and in some cases even Social Security numbers. Is it employee or customer data? As DataBreaches.net pointed out, PSE did not mention if this data belongs to PSE employees or PSE customers --such as those who registered for the Pacers online shop to buy gear and memorabilia. By the wide range of exposed information, at first sight, it may appear that it's both --although, ZDNet reached out to PSE via email earlier today to clarify this issue in the company's confusing breach disclosure. A phone number that potential victims can call and get more information about the incident and see if they are impacted is available on the Pacers website. PSE also published information on how impacted individuals can protect themselves against fraud and identity theft. The company said it did not receive any reports that personal data has been misused. Source
  6. Later today, eBay will begin asking all of its 112 million customers to change their passwords, in the wake of a newly discovered database breach. The breach compromised a database containing a list of encrypted passwords that, once released in the wild, could potentially be decrypted through publicly available tools. As a result, eBay is asking users to change passwords as soon as possible. Officials say no financial data was implicated, and the company hasn't found any evidence of unauthorized activity resulting from breach. The attack itself took place some time between late February and early March, when attackers obtained a group of employee log-in credentials, allowing access to the larger database. Even after the attack, eBay wasn't aware of the compromise until two weeks ago, and it took detailed forensic analysis to implicate the password database, resulting in today's announcement. In addition to passwords, the database contained basic login information like name, email, phone number, address and date of birth, but officials stressed that no confidential or personal information was included in the breach. Paypal was not involved in the breach, as PayPal data is kept on a separate network with higher levels of encryption. Still, a site-wide password reset is generally seen as the best response to this kind of breach. eBay also reminded users to make the change at any other sites where they had used the same password, a bad security practice that is nonetheless widespread. Source
×
×
  • Create New...