时间:2025-04-02 04:46:38 来源:网络整理编辑:綜合
If you perform a very specific query in the search field of online code repository Github, where man
If you perform a very specific query in the search field of online code repository Github, where many Slack bot projects are stored, you can get info that potentially lets you access a trove of corporate data, including companies' internal chats and files.
This is because a lot of Slack bot developers -- and there are a lot of them, since building a Slack bot is quite easy -- included their Slack tokens (personal Slack account credentials) directly in the code, which they share publicly on Github.
SEE ALSO:How do I make Slack apps?The issue was discovered by security company Detectify, which notified Slack about it on March 26. Detectify managed to find "thousands" of such tokens with a simple GitHub search. The story was first reported by Quartz.
Tokens of all types aren't uncommon on GitHub, but the problem is made worse by the way Slack tokens are constructed. In case of private tokens and custom bot tokens, they're a string of characters using these formats:
xoxp-XXXXXXXXX-XXXXXXXXXXXXXXXXXXX
xoxb-XXXXXXXXX-XXXXXXXXX-XXXXXXXXX-XXXXXX
Simply searching for the four letter prefixes on GitHub will net you a lot of tokens in plain text, which we were able to replicate.
If you've never built anything on the Slack platform, you may think this doesn't affect you, and in many cases that's true. But in larger business organizations, it's quite possible that some team member had built a Slack bot and inadvertently revealed their Slack token, potentially exposing company data.
Outsiders can easily gain access to internal chat conversations, shared files, direct messages and even passwords.
"Using the tokens it’s possible to eavesdrop on a company. Outsiders can easily gain access to internal chat conversations, shared files, direct messages and even passwords to other services if these have been shared on Slack," writes Detectify.
The researchers at Detectify have found tokens belonging to Fortune 500 companies, payment providers, Internet service providers health care providers, advertising agencies, university classes and newspapers, among other organizations. And using those tokens, they revealed database credentials, private messages and login details for other services.
The good news is the problem has largely already been fixed. Slack responded to the problem, telling Detectify they've “revoked the tokens you reported, notified affected users and team owners directly, and that we’ll be doing that proactively going forward”.
In other words, if someone makes the same mistake again, Slack will disable the tokens and warn them -- as seen in the message Slack recently started sending to some developers.
Developers, in general, should take care not to place tokens directly in the code and use environment variables instead. Slack admins can make sure only Team Owners and selected Slack members can create tokens and integrations; the option is in Slack's Admin Settings.
Mashablehas contacted Slack about the issue. "Slack is clear and specific that tokens should be treated just like passwords. We warn developers when they generate a token never to share it with other users or applications," a Slack spokesperson said in an email.
According to the spokesperson, Slack will continue to improve its documentation and communications to make sure developers understand this.
"For privacy reasons, we are not sharing information about the teams impacted, however, all of the reported tokens were disabled, as well as others we proactively found. We notified both the users who created the tokens, as well as the owners of affected teams," she wrote.
A popular platform for corporate communication (disclosure: We use Slack at Mashable), Slack boasted more than 2.3 million daily active users in February.
Have something to add to this story? Share it in the comments.
WhatsApp announces plans to share user data with Facebook2025-04-02 04:38
英媒專欄吹爆渣叔:夥伴 、羈絆 一起踏上四冠之旅2025-04-02 04:31
亞洲杯+亞冠官方:於大寶生日快樂 不可多得的鋒衛搖擺人2025-04-02 04:00
皇馬更衣室瘋狂時 貝爾如坐針氈如芒刺背如鯁在喉2025-04-02 03:52
Whyd voice2025-04-02 03:48
山東青年軍防守端進步明顯 兩連敗也有鍛煉意義2025-04-02 03:48
多特將貝林厄姆視為球隊新核心 利物浦皇馬欲挖角2025-04-02 03:17
廣州隊VS川崎前鋒首發:門將何立攀仍舊出戰 葉潤標登場2025-04-02 02:39
Tourist survives for month in frozen New Zealand wilderness after partner dies2025-04-02 02:37
東亞杯易地日本派J聯賽球員參賽 將為躋身世界杯名單而競爭2025-04-02 02:03
Carlos Beltran made a very interesting hair choice2025-04-02 04:33
京媒:網傳東亞杯賽程版本不實 比賽已易地賽程將會調整2025-04-02 04:11
國足官方:徐新生日快樂 十二強賽最後6戰全部首發2025-04-02 03:49
津媒:卡爾德克上訴至國際足聯 深圳隊或被禁止轉會2025-04-02 03:34
This 'sh*tpost' bot makes terrible memes so you don't have to2025-04-02 03:07
廣州隊VS川崎前鋒首發:門將何立攀仍舊出戰 葉潤標登場2025-04-02 02:59
哈維談諾坎普失陷:像在家裏被搶劫 完全不似主場2025-04-02 02:54
真升降機!富勒姆時隔一賽季重返英超 近5年3升2降2025-04-02 02:50
Sound the alarms: Simone Biles finally met Zac Efron2025-04-02 02:49
痛下殺手!巴黎欲肢解阿根廷幫 除梅西外全部清洗2025-04-02 02:27