Selfhosted

62,325 readers

5,950 active

1,196 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

moderators

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

18-Year-Old NGINX Rewrite Module Flaw Enables Unauthenticated RCE (thehackernews.com)

submitted 4 months ago* (last edited 4 months ago) by eager_eagle@lemmy.world to c/selfhosted@lemmy.world

15 comments fedilink hide all child comments

Update your nginx instances

cross-posted from: https://lemmy.world/post/46851448

Affected an non-affected versions https://nginx.org/en/security_advisories.html
CVE record https://www.cve.org/CVERecord?id=CVE-2026-42945
CVE details https://nvd.nist.gov/vuln/detail/CVE-2026-42945
PoC https://github.com/DepthFirstDisclosures/Nginx-Rift

CVE - Common Vulnerabilities and Exposures system
RCE - Remote Code Execution
PoC - Proof of Concept

you are viewing a single comment's thread
view the rest of the comments

[–] skankhunt42@lemmy.ca 5 points 4 months ago (3 children)

Yep. I wasn't affected thankfully. Didn't realise I was flexing, sorry. Just happy most of my stack is automated and it's quite low maintenance at this point.

Where do I draw the line then? Serious question. If updating every couple hours is bad, then what's safe?

permalink

fedilink

source

parent

hideshow 3 child comments

[–] GreenKnight23@lemmy.world 3 points 4 months ago

for corporate services we do every 30 days. which is standard. emergency patches get direct support and resolved quickly.

permalink

fedilink

source

parent

[–] JaddedFauceet@lemmy.world 2 points 4 months ago

idk, also it is not about the frequency you update, it is usually about how long has it been since package is published to the internet

see concept of min release age https://pnpm.io/blog/releases/10.16

i wonder if other package manager have similar thing or not

permalink

fedilink

source

parent

[–] pinhead77@piefed.social 1 point 4 months ago* (last edited 4 months ago)

You can use pnpm instead of npm. pnpm has a "Delay dependency updates" feature where you can install package versions that are x old only.
See https://pnpm.io/supply-chain-security#delay-dependency-updates

Edit: I just found out, that this can also be specified in npm and yarn: https://gist.github.com/mcollina/b294a6c39ee700d24073c0e5a4e93104

permalink

fedilink

source

parent