Introducing HAR Sanitizer: secure HAR sharing
On Wednesday, October 18th, 2023, Cloudflare’s Security Incident Response Team (SIRT) discovered an attack on our systems that originated from an authentication token stolen from one of Okta’s support systems. No Cloudflare customer information or systems were impacted by the incident, thanks to the real-time detection and rapid action of our Security Incident Response Team (SIRT) in tandem with o
Announcing D1: our first SQL database
We announced Cloudflare Workers in 2017, giving developers access to compute on our network. We were excited about the possibilities this unlocked, but we quickly realized — most real world applications are stateful. Since then, we’ve delivered KV, Durable Objects, and R2, giving developers access to various types of storage. Today, we're excited to announce D1, our first SQL database. While the w
Cloudflareã®cdnjsã«ãŠã‘ã‚‹ä»»æ„コード実行
ã¯ã˜ã‚ã«(English version is also available.) cdnjsã®é‹å–¶å…ƒã§ã‚ã‚‹Cloudflareã¯ã€HackerOne上ã§è„†å¼±æ€§é–‹ç¤ºåˆ¶åº¦(Vulnerability Disclosure Program)ã‚’è¨ã‘ã¦ãŠã‚Šã€è„†å¼±æ€§ã®è¨ºæ–行為を許å¯ã—ã¦ã„ã¾ã™ã€‚ 本記事ã¯ã€å½“該制度を通ã—ã¦å ±å‘Šã•ã‚ŒãŸè„†å¼±æ€§ã‚’Cloudflareã‚»ã‚ュリティãƒãƒ¼ãƒ ã®è¨±å¯ã‚’å¾—ãŸä¸Šã§å…¬é–‹ã—ã¦ã„ã‚‹ã‚‚ã®ã§ã‚ã‚Šã€ç„¡è¨±å¯ã®è„†å¼±æ€§è¨ºæ–行為を推奨ã™ã‚‹ã“ã¨ã‚’æ„図ã—ãŸã‚‚ã®ã§ã¯ã‚ã‚Šã¾ã›ã‚“。 CloudflareãŒæä¾›ã™ã‚‹è£½å“ã«è„†å¼±æ€§ã‚’発見ã—ãŸå ´åˆã¯ã€Cloudflareã®è„†å¼±æ€§é–‹ç¤ºåˆ¶åº¦ã¸å ±å‘Šã—ã¦ãã ã•ã„。 è¦ç´„cdnjsã®ãƒ©ã‚¤ãƒ–ラリ更新用サーãƒãƒ¼ã«ä»»æ„ã®ã‚³ãƒ¼ãƒ‰ã‚’実行ã™ã‚‹ã“ã¨ãŒå¯èƒ½ãªè„†å¼±æ€§ãŒå˜åœ¨ã—ã€çµæžœã¨ã—ã¦cdnjsを完全ã«ä¾µå®³ã™ã‚‹ã“ã¨ãŒå‡ºæ¥ã‚‹çŠ¶æ…‹ã ã£ãŸã€‚ ã“ã‚Œã«ã‚ˆã‚Šã€ã‚¤ãƒ³ã‚¿ãƒ¼ãƒãƒƒãƒˆä¸Šã®ã‚¦ã‚§ãƒ–サイトã®å†…12.7
How and why the leap second affected Cloudflare DNS
How and why the leap second affected Cloudflare DNS2017-01-01 At midnight UTC on New Year’s Day, deep inside Cloudflare’s custom RRDNS software, a number went negative when it should always have been, at worst, zero. A little later this negative value caused RRDNS to panic. This panic was caught using the recover feature of the Go language. The net effect was that some DNS resolutions to some Clou
Incident report on memory leak caused by Cloudflare parser bug
Last Friday, Tavis Ormandy from Google’s Project Zero contacted Cloudflare to report a security problem with our edge servers. He was seeing corrupted web pages being returned by some HTTP requests run through Cloudflare. It turned out that in some unusual circumstances, which I’ll detail below, our edge servers were running past the end of a buffer and returning memory that contained private info
1
ランã‚ング
ランã‚ング
ランã‚ング
リリースã€éšœå®³æƒ…å ±ãªã©ã®ã‚µãƒ¼ãƒ“スã®ãŠçŸ¥ã‚‰ã›
最新ã®äººæ°—エントリーã®é…ä¿¡
j次ã®ãƒ–ックマーク
kå‰ã®ãƒ–ックマーク
lã‚ã¨ã§èªã‚€
eコメント一覧を開ã
oページを開ã
{{#tags}}- {{label}}
{{/tags}}