#security

1994 posts · Last used 10h

Boosted by @fedicat@pc.cafe
BotKit security updates: 0.4.12 and 0.5.9 If you use BotKit 0.4.0–0.4.11 or 0.5.0–0.5.8, update to a patched release now. These releases shipped with Fedify versions affected by missing deadlines in WebFinger lookups (GHSA-9pmv-w936-hj3f), outbound activity delivery (GHSA-fq5h-gjhp-g75x), and NodeInfo lookups (GHSA-64hq-2hgr-q4pm), as well as an origin-check bypass for embedded objects (GHSA-r388-57j3-5fgp). GHSA-9pmv-w936-hj3f can stall a lookup when your bot resolves a handle on a slow remote server. Inbox processing can also reach WebFinger when Fedify falls back to it while re-fetching an incoming activity. The fix gives each WebFinger lookup a single 10-second deadline, including redirects. Non-portable actor handle resolution shares that budget across the initial lookup and alias checks. GHSA-fq5h-gjhp-g75x lets a slow remote inbox hold delivery workers and connections open, potentially delaying deliveries to other servers. The fix gives each signed or unsigned delivery attempt a single 30-second deadline, including redirects and signature retries. Timed-out attempts can be retried under your configured delivery schedule. GHSA-64hq-2hgr-q4pm affects applications that explicitly query NodeInfo on remote servers. A slow server can stall the lookup; ordinary inbound federation does not trigger it. The fix gives the entire lookup a 10-second deadline by default and stops following redirects when a URL repeats. GHSA-r388-57j3-5fgp affects how Fedify reads embedded objects from remote JSON-LD. A remote actor could send a signed activity that caused a BotKit handler to receive forged content under another server's object ID. The fix applies the embedded object's origin check even when its parent has no id. Fedify 2.3.16 also fixes two issues in @fedify/backfill, which BotKit does not use. If your application uses that package separately, upgrade it too. GHSA-x58x-xx7h-7rh4 allowed backfill to return forged embedded content under another server's ID; the fix fetches cross-origin objects by ID instead of trusting the embedded copy. GHSA-h3jv-px69-2gpj affected custom loaders that did not validate the origin of returned IDs; the fix rejects results whose ID origin differs from the requested origin, even after a cross-origin redirect. See Fedify's own announcement for backfill upgrade guidance. The first patched BotKit releases, and the versions we recommend installing, are 0.4.12 and 0.5.9. They require Fedify 2.1.32 and 2.3.16, respectively. These are the two supported BotKit lines under the security policy. If you're on an older line, move to a supported release. For BotKit 0.5.x, install @fedify/botkit 0.5.9 using the command for your package manager: npm install @fedify/botkit@0.5.9 yarn add @fedify/botkit@0.5.9 pnpm add @fedify/botkit@0.5.9 bun add @fedify/botkit@0.5.9 deno add jsr:@fedify/botkit@0.5.9 For BotKit 0.4.x, install @fedify/botkit 0.4.12: npm install @fedify/botkit@0.4.12 yarn add @fedify/botkit@0.4.12 pnpm add @fedify/botkit@0.4.12 bun add @fedify/botkit@0.4.12 deno add jsr:@fedify/botkit@0.4.12 Check your installed versions or lockfile for older copies of @fedify/fedify, @fedify/vocab, and @fedify/webfinger. The patched versions start at 2.1.32 on the 2.1.x line and 2.3.16 on the 2.3.x line. If you depend on these packages directly, update those dependencies too. If your dependency constraints prevent an upgrade, change them explicitly. After updating, redeploy all web and worker processes. Thanks to zx (@manus-pi) for reporting the WebFinger, delivery, and NodeInfo issues to Fedify, and to @manus-use for reporting the WebFinger and NodeInfo issues. Thanks also to @hongminhee@hollo.social for reporting the embedded-object origin-check bypass and the cross-origin backfill issue, and to @z9mb1@hackers.pub for reporting the custom backfill loader issue. If anything is unclear, feel free to ask on GitHub Discussions or Matrix.
0
0
2
0
Pixelfed added the ability to limit DMs to accounts you follow 8 years ago. Then we introduced the federated ability to disable comments on your posts 7 years ago. 2 years ago we added Parental Controls. But we can still improve and give our community the features and tools they need to stay safe and secure. The Pixelfed 2027 roadmap includes several new privacy and safety features, I'll share more info soon. #pixelfed #privacy #safety #security
4
0
5
1
One of the positive things that happened yesterday was reconnecting with a group of colleagues I hadn't spoken to in a long time. They said something interesting: "For years, many of us thought OpenBSD was a bit paranoid. That they were going too far. Then came the flood of CVEs, RCEs, and all the rest, and OpenBSD has been holding up remarkably well. They weren't overreacting. They had simply understood a few things better than the rest of us." That last sentence brought a satisfied smile to my face. #OpenBSD #RunBSD #IT #SysAdmin #Security
7
8
4
0
Replying to
@mutualaidspace The submission form includes mandatory security verification to prevent spam and abuse. We do not bypass these security measures, manually process submissions that fail verification, or accept mutual aid requests by email. Thank you for your understanding. Please take care and stay safe. #announcement #fediverse #mutualaidspace #mutualaid #mutualaidrequest #mutualaidsaveslives #security @comrade @mutualaid@fedigroups.social @mutualaid @wrzky @wrzky@kolektiva.social @wrzky@flipboard.social
0
0
0
0
Me: “Static websites are great for security! No CMS, no database, no PHP, no plugins. Just a few innocent HTML files. What could possibly go wrong?” nginx: “Hold my CVE.” Me: “Well, technically, I said the website was secure. I never said anything about the web server.” And this, kids, is why we can’t have nice things. Not even an index.html. #nginx #SysAdmin #Security #StaticSites
58
0
29
0
📣 PHP security releases are scheduled for Thursday, 19 November 2026, 14:00–14:30 UTC, as part of our regular four-week release cycle. All supported PHP versions are affected. Highest severity: CRITICAL. Issues at this severity require non-default configuration or uncommon setups. Please prepare to upgrade promptly once the releases are available. 🔗 https://www.php.net/archive/2026.php#2026-11-18-1 #PHP #Release #Security
23
0
80
0