{"id":11570,"date":"2018-02-22T19:17:04","date_gmt":"2018-02-23T03:17:04","guid":{"rendered":"http:\/\/www.palada.net\/index.php\/2018\/02\/22\/news-5341\/"},"modified":"2018-02-22T19:17:04","modified_gmt":"2018-02-23T03:17:04","slug":"news-5341","status":"publish","type":"post","link":"https:\/\/www.palada.net\/index.php\/2018\/02\/22\/news-5341\/","title":{"rendered":"Chase ‘Glitch’ Exposed Customer Accounts"},"content":{"rendered":"

Credit to Author: BrianKrebs| Date: Fri, 23 Feb 2018 00:35:30 +0000<\/strong><\/p>\n

Multiple Chase.com<\/strong> customers have reported logging in to their bank accounts, only to be presented with another customer’s bank account details. Chase has acknowledged the incident, saying it was caused by an internal “glitch” Wednesday evening that did not involve any kind of hacking attempt or cyber attack.<\/span><\/p>\n

\"\"<\/p>\n

Trish Weller<\/strong>, director of communications for the retail side of JP Morgan Chase<\/strong>, said the incident happened Wednesday evening, for “a pretty limited number of customers” between 6:30 pm\u00a0 and 9 pm ET who “sporadically during that time while logged in to chase.com could see someone else\u2019s account details.”<\/span><\/p>\n

“We know for sure the glitch was on our end, not from a malicious actor,” Weller said, noting that Chase is still trying to determine how many customers may have been affected. “We’re going through Tweets from customers and making sure that if anyone is calling us with issues we’re working one on one with customers. If you see suspicious activity you should give us a call.”<\/span><\/p>\n

Weller urged customers to “practice good security hygiene” by regularly reviewing their account statements, and promptly reporting any discrepancies. She said Chase is still working to determine the precise cause of the mix-up, and that there have been no reports of JPMC commercial customers seeing the account information of other customers.<\/span><\/p>\n

“This was all on our side,” Well said. “I don’t know what did happen yet but I know what didn’t happen. What happened last night was 100 percent not the result of anything malicious.”<\/span><\/p>\n

The account mix-up was documented on Wednesday by Fly & Dine<\/a>, an online publication that chronicles the airline food industry. Fly & Dine included screenshots of one of their writer’s spouses logged into the account of a fellow Chase customer with an Amazon and Chase card and a balance of more than $16,000.<\/span><\/span><\/p>\n

Kenneth White<\/a>, a security researcher and director of the Open Crypto Audit Project<\/a>, said the reports he\u2019s seen on Twitter and elsewhere suggested the screwup was somehow related to the bank\u2019s mobile apps. He also said the Chase retail banking app offered an update first thing Thursday morning. <\/span><\/p>\n

Chase says the oddity occurred for both chase.com and users of the Chase mobile app.\u00a0<\/span><\/p>\n

“We don’t have any evidence it was related to any update,” Weller said.<\/p>\n

\u201cThere\u2019s only so many kind of logic errors where Kenn logs in and sees Brian\u2019s account,\u201d White said.\u00a0 <\/span>\u201cIt can be a devil to track down because every single time someone logs in it\u2019s a roll of the dice \u2014 maybe they get something in the warmed up cache or they get a new hit. It\u2019s tricky to debug, but this is like as bad as it gets in terms of screwup of the app.\u201d<\/span><\/p>\n

White said the incident is reminiscent of a similar glitch at online game giant Steam<\/a>, which caused many customers to see account information for other Steam users for a few hours. He said he suspects the problem was a configuration error someplace within Chase.com “caching servers,” which are designed to ease the load on a Web application by periodically storing some common graphical elements on the page — such as images, videos and GIFs.<\/p>\n

“The images, the site banner, all that’s fine to be cached, but you never want to cache active content or raw data coming back,” White said. “If you’re CNN, you’re probably caching all the content on the homepage. But for a banking app that has access to live data, you never want that to be cached.”<\/span><\/p>\n

“It\u2019s fairly easy to fix once you identify the problem,” he added. “I can imagine just getting the basics of the core issue [for Chase] would be kind of tricky and might mean a lot of non techies calling your Tier 1 support people.”<\/span><\/p>\n

Update, 8:10 p.m. ET:<\/strong> Added comment from Chase about the incident affecting both mobile device and Web browser users.<\/p>\n

https:\/\/krebsonsecurity.com\/feed\/<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"

<\/p>\n

Credit to Author: BrianKrebs| Date: Fri, 23 Feb 2018 00:35:30 +0000<\/strong><\/p>\n

Multiple Chase.com customers have reported logging in to their bank accounts, only to be presented with another customer’s bank account details. Chase has acknowledged the incident, saying it was caused by a two an internal “glitch” Wednesday evening that did not involve any kind of hacking attempt or cyber attack.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"colormag_page_container_layout":"default_layout","colormag_page_sidebar_layout":"default_layout","footnotes":""},"categories":[10643,10642],"tags":[16740,17601,17602,17603,17604,17605,17606],"class_list":["post-11570","post","type-post","status-publish","format-standard","hentry","category-independent","category-krebs","tag-a-little-sunshine","tag-account-mix-up","tag-chase-com","tag-fly-dine","tag-kenneth-white","tag-open-crypto-audit-project","tag-trish-weller"],"_links":{"self":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/11570","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/comments?post=11570"}],"version-history":[{"count":0,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/posts\/11570\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/media?parent=11570"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/categories?post=11570"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.palada.net\/index.php\/wp-json\/wp\/v2\/tags?post=11570"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}