Account

Posts of Gift.亚信礼物买卖频道

newest first

#1215Textedited
Views252−85%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
3 h210
19 h238
32 h252
  1. After 24 hours238
  2. Total to date252
#1214Photo
Views2,176+33%vs avg
Forwards2
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
9 h2,146
25 h2,176
  1. After 24 hours2,176
  2. Total to date2,176
#1213Text

📛 Telegram 插件漏洞及创始人评论 在 V12 和 Joel Eriksson (OwariDa) 报告 Telegram 新功能——插件存在漏洞后,针对 Telegram 的负面评论如潮水般涌来。 ➖ 发生了什么 • 11 月 9 日至 10 日,Telegram 发布了 Android 和 Windows 应用程序的 HTML 插件。 • 11 月 11 日,V12 和 Joel Eriksson (OwariDa) 报告称,该新功能存在漏洞,可能导致远程代码执行 (RCE)。 • 同天,Telegram 通过服务器更新修复了该漏洞。 • 11 月 13 日,帕维尔·杜罗夫表示,不存在问题,因为利用该漏洞需要与第三方机器人或插件进行交互。 • 同样在 11 月 13 日,“卡斯帕斯基实验室”记录到了一些通过特定频道和机器人利用该漏洞的尝试,前提是激活了插件的交互功能(包括通过“start”命令)。 可能卡斯帕斯基的数据属于在完全禁用插件之前的时期。目前,该功能已停止工作。 ➖ 杜罗夫的立场 • 无论人们说什么,创始人的说法在技术上是正确的,因为该漏洞不是“零点击”漏洞,仅接收消息本身是不够的。 要触发它,需要与插件或机器人进行主动交互。 “仅通过接收消息即可入侵”的说法是错误的。 • 然而,研究人员的观点是正确的,即存在问题在于插件引擎,该引擎在特定条件下会触发。 • 尽管 Telegram 的服务器补丁可以过滤和阻止恶意代码,但问题仍然存在。 研究人员在报告中对 JavaScript 引擎 (QuickJS) 的批评,是因为该引擎没有进行严格的隔离。 ➖ 关于 V12 V12 是一家成立于 2026 年的美国初创公司。该公司开发了一个自主 AI 代理,用于查找漏洞(安全攻防)。因此,漏洞是由 AI 发现的。 考虑到插件功能本身也是由 AI 参与开发的,这一事件突出了“AI 编码”的风险,以及对由神经网络生成的代码质量的更高关注的必要性。 ➖ 反应 负面评论是不正常的,因为它往往与事实不符,并且具有非技术性。 不幸的是,针对 Telegram 和 TON 的负面评论主要来自独联体国家的用户。 考虑到 Telegram 长期以来一直受到情报机构和竞争对手的压力,因此有必要区分技术事实和信息浪潮。 您能区分吗?

Open in Telegram
Views338−79%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
10 h324
25 h338
  1. After 24 hours338
  2. Total to date338
#1212Text
Views370−77%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h313
13 h338
25 h370
  1. After 1 hour313
  2. After 24 hours370
  3. Total to date370
#1211Photo
Views330−80%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
6 h273
30 h296
70 h330
  1. After 6 hours273
  2. After 24 hours296
  3. Total to date330
#1210Photo
Views420−74%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
10 h363
35 h390
71 h420
  1. Total to date420
#1209Text
Views440−73%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
11 h381
31 h409
72 h440
  1. After 24 hours409
  2. Total to date440
#1208Text
Views437−73%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
5 h362
17 h379
29 h394
61 h427
77 h437
  1. After 6 hours362
  2. After 24 hours394
  3. Total to date437
#1206Attachment
Views5,055+209%vs avg
Forwards5
Reactions5
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
3 h1,443
15 h3,355
27 h4,486
75 h5,055
  1. After 24 hours4,486
  2. Total to date5,055
#1204Photoalbum
Views1,803+10%vs avg
Forwards1
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
11 h540
36 h607
72 h1,803
  1. Total to date1,803
#1203Photoalbum
Views4,883+198%vs avg
Forwards1
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
11 h2,108
36 h3,689
72 h4,883
  1. Total to date4,883
#1202Photoedited
Views465−72%vs avg
Forwards2
Reactions0
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
4 h424
14 h445
28 h458
43 h465
  1. After 24 hours458
  2. Total to date465
#1200Photo
Views514−69%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
12 h456
34 h490
36 h491
70 h514
  1. Total to date514
#1192Photodeleted
Views404−75%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
5 h388
12 h404
  1. After 6 hours388
  2. Total to date404
#1190Photo
Views345−79%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
3 h342
8 h345
  1. After 6 hours345
  2. Total to date345
#1188Photodeleted
Views405−75%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
4 h398
11 h405
  1. Total to date405
#1184Photo
Views7,924+384%vs avg
Forwards1
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
5 h398
10 h400
19 h7,924
  1. After 6 hours398
  2. After 24 hours7,924
  3. Total to date7,924
#1182Photodeleted
Views385−76%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
4 h374
10 h385
  1. After 6 hours374
  2. Total to date385
#1180Photodeleted
Views434−73%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
4 h413
10 h420
16 h434
  1. After 24 hours434
  2. Total to date434
#1178Photo
Views541−67%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h477
5 h503
10 h516
26 h539
27 h541
  1. After 1 hour477
  2. After 6 hours503
  3. After 24 hours539
  4. Total to date541
#1176Photodeleted
Views385−76%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
3 h381
8 h385
  1. After 6 hours385
  2. Total to date385
#1174Photodeleted
Views390−76%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
1 h366
3 h377
9 h390
  1. After 1 hour366
  2. Total to date390
#1172Photodeleted
Views417−75%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
3 h396
7 h398
16 h417
  1. After 6 hours398
  2. After 24 hours417
  3. Total to date417
#1170Photodeleted
Views458−72%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
2 h438
6 h451
10 h458
  1. After 6 hours451
  2. Total to date458
#1168Photodeleted
Views387−76%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h197
4 h383
9 h387
  1. After 1 hour197
  2. After 6 hours383
  3. Total to date387
#1166Photodeleted
Views437−73%vs avg
Forwards0
Reactions—
Comments—
Views growthHide views growth

Views growth

Hours after publication

Show as table
Hours after publicationViews
0 h0
3 h427
7 h436
8 h437
  1. After 6 hours436
  2. Total to date437