Re:Synology Security Advisory
by benoau on Thursday November 19, 2026 @08:59PM
(#50569210)
In Synology's case a lot of their stuff is just legacy even though they don't describe it that way, I think most of their apps have not been worked on for years, at this point I wonder if they even have much more than a skeleton crew working on their software at all.
Re:Synology Security Advisory
by Gigachad on Thursday November 19, 2026 @06:38PM
(#50568162)
You should design your home server with two layers of security. The actual server and apps should be secured in the same way you would a public application, and then wireguard on top. That way an exploit needs to compromise both layers at the same time. And with auto updates enabled the chance of that happening is low.
Re:Synology Security Advisory
by TedDoesntTalk on Thursday November 19, 2026 @09:04PM
(#50569252)
I don’t even bother with wireguard or tailscale anymore. They will have vulnerabilities discovered, if they don’t already. Not all vulns are made public.
Nothing gets through the firewall anymore. So now my only vulnerability (I hope) is the firewall, OPNsense.
Re:Synology Security Advisory
by whilenot-dev on Friday November 20, 2026 @07:45AM
(#50573929)
WireGuard does not even respond at all[0] to unauthorized clients, so the forwarded port stays invisible to unwanted clients. AFAIK SSH always gives a response[1].
Re:Synology Security Advisory
by LoganDark on Thursday November 19, 2026 @06:00PM
(#50567783)
mTLS is the one that requires a client certificate. right? It can be quite difficult to get protocols other than HTTPS to behave well with that, mostly because the application has to worry about it and many don't bother.
Re:Synology Security Advisory
by LoganDark on Thursday November 19, 2026 @06:36PM
(#50568142)
I think if you want mTLS to have any significance, the application itself has to support it, otherwise you're just doing a VPN again and there's no good reason to use it over Wireguard (especially because an mTLS server will respond to port scans and a Wireguard server will not)
Re:Synology Security Advisory
by QuantumNomad_ on Thursday November 19, 2026 @07:15PM
(#50568450)
WireGuard is also very much like SSH private keys.
A basic config to set up a VPN that only adds access to services on the VPN itself is very short and simple, both for WireGuard server and for WireGuard clients.
You can run the WireGuard server from your home computer. For example on your NAS machine itself or some other machine you have at home. And open the port for WireGuard to the outside.
Also some routers can run WireGuard server on the router. For example Mikrotik routers have WireGuard server built in and ready to configure [0]. Routers running OpenWrt can too [1].
Or you can rent a small VPS and use that as your WireGuard server.
And then, either which where you run the WireGuard server, run the WireGuard client on your laptops, iOS and Android devices, and connect client apps using VPN internal IP addresses. And your NAS etc too, if the WireGuard server isn’t running on the NAS machine itself.
It really is quite quick to set up with server and all clients across devices.
The only real hurdle is that on iOS you have to turn the VPN back on manually after reboot and which is sometimes easily forgotten if you only use your self hosted services occasionally. But you quickly realize oh right I have to open the WireGuard app and turn on the VPN again whenever you try to use one of your self hosted services and the client isn’t connecting.
Re:Synology Security Advisory
by 8fingerlouie on Thursday November 19, 2026 @06:07PM
(#50567839)
Compared to faffing around with certificates, Wireguard or if you're lazy, Tailscale, is a breeze to setup.
Generate the config, one per client, setup the client to only route specific RFC1918 networks and disable on well known wifi networks, and that's it. It literally works for years without any maintenance.
Tailscale is easier (presumably), but also puts a corporate entity between you and your data.
Re:Synology Security Advisory
by devilbunny on Thursday November 19, 2026 @07:33PM
(#50568607)
Tailscale is ridiculously easy, and headscale is a thing. It doesn't support everything corporate Tailscale does, but it covers the basics of "get me into my network from anywhere". You can run it on a $1/month VPS that has a public IPv4 address.
I don't work with computers professionally, at all. It still only took me about 2 hours to get the VPS, get Debian going on it, set up headscale, and connect to it from home. Do I still use corporate Tailscale? Yes, it has some features that aren't beautifully supported on headscale, and so for the moment I'm fine with that. But I do have my backup plan in place if I need it.
Re:Synology Security Advisory
by rlt on Thursday November 19, 2026 @07:58PM
(#50568803)
Personally I’d rather let Tailscale manage securing the public-facing service than use Headscale. Tailnet Lock seems like a good compromise. And as much as I’d like to use it, I don’t trust Tailscale SSH.
Re:Synology Security Advisory
by letsseeok on Friday November 20, 2026 @04:01AM
(#50572021)
> I don't work with computers professionally, at all.
You trust yourself with a VPS and correctly configuring a beast such a Debian?
I don't mean to be harsh but even as a professional developer I'm frequently humbled by our grumpy sysadmins on (to me) arcane stuff I didn't knew existed.
Re:Synology Security Advisory
by aborsy on Thursday November 19, 2026 @09:06PM
(#50569266)
A corporate in the control plane is not an issue for me. But what if their infrastructure is compromised?
They are prime targets and have large attack surface. Even bigger companies are frequently compromised. It's a matter of time before it becomes publicly known.
Re:Synology Security Advisory
by Liuser on Thursday November 19, 2026 @06:28PM
(#50568058)
VPNs these days are far easier to configure than mTLS (which often need proxies on both server and client side to handle the TLS terminations and needing to worry more with certificate lifecycle).
mTLS is a better option for distributed systems (service to service mesh networks for attestation of workload identities) instead of for human users.
Re:Synology Security Advisory
by bigwheels on Thursday November 19, 2026 @06:47PM
(#50568238)
Strongly agree, Tailscale / WG is the way go. Unless something needs to be available to randos on the Internet, in which case mTLS is still a huge headache.
Re:Synology Security Advisory
by landgenoot on Thursday November 19, 2026 @07:00PM
(#50568351)
I want to make sure every picture I take will be backed up to the NAS.
Do I turn on the VPN when I take a picture and turn it off when finished? Every time?
What if I need multiple VPN's? Living in a country that has a bad geoip reputation, it's already a struggle of switching on and off for individual websites to work.
Re:Synology Security Advisory
by akerl_ on Friday November 20, 2026 @07:07AM
(#50573601)
The thing that’s nice about using WireGuard here is that it works for any app on my phone; they don’t have to individually support it and I don’t have to individually configure certs for them.
I have one on-demand VPN with a list of internal IPs to route.
Re:Synology Security Advisory
by cloudfudge on Thursday November 19, 2026 @07:41PM
(#50568664)
How many mTLS configs are anything but all-or-nothing access? It is so common for an app to slap mTLS on the endpoints and make the rule "anyone with a valid cert is admin on this API; anyone else gets 401." This is a step back towards a superuser/regular-user model.
Now if you're going to use mTLS as the basis for mature authn/authz, that's a different story. But I never see anyone do that.
Re:Synology Security Advisory
by Liuser on Friday November 20, 2026 @12:57AM
(#50570690)
Yeah that I get, but I’m disputing that the tool (mTLS) is not at fault for being misused, authz (rather the lack of it) is being misused. The tool (authn) is working fine.
Re:Synology Security Advisory
by cloudfudge on Friday November 20, 2026 @03:08AM
(#50571592)
We are saying the same thing. mtls is fine for authn. But nobody actually uses it for just that. They use it for both authn and authz. The authz policy is almost always just "identity != null".
If I told you not to use a power drill as a hammer, you wouldn't claim I'm saying the hammer is at fault for being a bad power drill.
Re:Synology Security Advisory
by Liuser on Friday November 20, 2026 @08:51AM
(#50574640)
Yes, this I agree with that. JWT is simpler to work with by virtue of remaining on http layer 7 and parsing claims out of JSON compared to working with extracting identity and other embeddings from x509.
I just take issue (maybe pedantically so) calling it a bad tool and blanket statements that no one uses it for just authn but for authz also. It’s not used for authz. The absence of authz shouldn’t be blamed on mTLS.
Re:Synology Security Advisory
by anonymousiam on Thursday November 19, 2026 @10:21PM
(#50569759)
There's a third-party repository for Synology that includes WireGuard. I've been using it for over a year now and it works great. (Presently posting this from Chenzhou, China where I have full access to my US-based Synology NAS courtesy of WireGuard and WSTunnel.)
Re:Synology Security Advisory
by dj68k on Thursday November 19, 2026 @06:27PM
(#50568051)
I agree. However, I also want to share photo albums with family and friends with Photo Station and/or Immich. I may also want to run Jellyfin so the same family and friends can watch my collection of... 'Linux ISOs'. Do I simply pinhole those TCP ports through my router and "hope for the best," or is there a better solution?
Re:Synology Security Advisory
by hamdingers on Thursday November 19, 2026 @06:33PM
(#50568107)
Run them in containers, put them behind a reverse proxy that does TLS, point fail2ban at the proxy logs. Use strong passwords. Take backups. Life isn't worth living without a little risk.
Re:Synology Security Advisory
by Gigachad on Thursday November 19, 2026 @06:39PM
(#50568170)
Wait out the current wave of madness. In a year or so we will have the most secure software ever seen. We also might start to see servers with Memory Tagging to block exploits not yet found.
Re:Synology Security Advisory
by greggsy on Friday November 20, 2026 @01:01AM
(#50570730)
/r/synology has been a sea of compromise posts these past weeks.
I personally think Synology are mostly at most fault here though - they shouldn’t be making it so easy for clueless users to do this. It’s basically advertised as a feature.
Very, very few consumer products make it that easy to set up and tie your own noose.
Re:Synology Security Advisory
by Scottn1 on Friday November 20, 2026 @01:29AM
(#50570896)
I set up two Synology for someone who needed to backup file. One unit at his office and one at home. He does 90% of his work at the office, but wants to be able to access them at home or weekends if needed. He works with very large video files and a cloud cost per month for 8-10tb and growing wasn't in his budget (couldn't afford it).
Synology was a perfect solution. Low-cost unit, stick a 15gb drive in it and do again for second unit. DSM is a breeze to work with and the built in rsync was pretty easy to setup and has been working seamlessly for a year now.
Just free willy opening ports and sticking a default setup NAS to the internet, I agree, is asking to be hacked. Tailscale was my preferred way to get them connected but there is no Tailscale Synology client, and if I remember, would required hacks to get one on it and working. Use long passwords for the user is first start. Then on both use the security settings to only accept the ONE IP from each other, even though only one of them is actually exposed to the internet. Also select the settings to install any security updates automatically. Logs show this has all been working good to protect the units. The only catch so far is the IP of his house changed once in the year, being it isn't static, but simply changing it on the sending unit to new one fixed it in about 3 minutes.
I'm thinking of replicating this setup for myself to backup all PC's and phones in my household and syncing to another unit I set up at my relative's house in another state while I visit over the holidays. It pays for itself in short time compared to a cloud provider.
I'm curious now after this CVE how long it will take the units to auto update to newest version after it becomes available to manually install.
Re:Synology Security Advisory
by tecleandor on Friday November 20, 2026 @05:19AM
(#50572648)
There is an official Tailscale package [0], although you might need to schedule a task for upgrades and fixing noetwork configuration on restart.
Anyway, I bought one for a client past year, and I won't buy nor recommend one ever again. It's a mess security and technically wise.
They're on a 4.4 kernel (even on recent devices), supposedly backporting security bugfixes. That also means that on a kernel so old you don't have the networking performance improvements and features of the last 10 years.
They're using a btrfs version they forked 10 years ago that they're maintaining out of tree, that also doesn't have any of the new features, and that's not compatible with recent btrfs versions. On top of that, they self built a super messy ACL system that's using a vmtouch version also from 10 years ago.
They always have super outdated libraries. They've been using PHP7.4 (EOLed 4 years ago) until past winter, and PHP8.1 until this summer.
I take a look to the running daemons and... their SMB daemon is based on 4.15.13 (from 2022). Nginx 1.23.1 (from 2022). chrony (it just says DEVELOPMENT version). net-snmp 5.9.3 (2022). rsync 3.1.2 (2015). Postgres 11.11 (2021). Not fun.
And I'm talking about a supported device that got a major OS upgrade this summer.
With this wave of AI security attacks, they don't have much time until something huge appears. Either that, or they use that AI to accelerate going back to mainline versions of the software they use.
Re:Synology Security Advisory
by ezst on Friday November 20, 2026 @02:21AM
(#50571267)
And why would that be different than, say, asserting "You can't have debian/Linux exposed to the internet" (which we all agree is silly)? NAS are just your usual breed of Linux distros, and reputable brands come pre-hardened (it's easy to laugh at Synology, but they were as quick, if not faster to patch node/php and now nginx than most mainstream distros, and the bunch of kernel exploits relating to unsound crypto utilities didn't affect them to begin with because the modules were not compiled in).
Synology isn't a panacea (they put themselves in an awkward position with their btrfs fork, with constraints them to stay on an obsolete kernel branch and do a ton of patch shuffling and backporting), but is a much better posture to start homelabing from than, say, a raspbian in a shoebox.
Re:Synology Security Advisory
by dj68k on Thursday November 19, 2026 @05:36PM
(#50567482)
The oldest one I have still serving data at home is an 1813+ running DSM 7.1.1-42962 Update 9. It's inside my network and just does SMB1 and AFP for my retro computer collection and serves as a dumping ground for security camera footage. Really curious when Syno's going to finally cut this thing off from updates since it's been years since 7.2 came out and it didn't get it.
I just recently took a 415+ off the internet (it had Photo Station and Apache only exposed to the outside). I did the "resistor mod" on its JTAG connector to save its Atom from literally frying itself and it's also still working fine. As usual, the hardware far outlives the software.
Re:Synology Security Advisory
by aquariusDue on Thursday November 19, 2026 @06:13PM
(#50567917)
I know this is not relevant to the topic at hand but tangentially related:
Does anyone know of any UGREEN UGOS alternatives? I don't mind the terminal but friends prefer a web GUI and for some mundane stuff I too have started to (begrudgingly) prefer it.
Re:Synology Security Advisory
by edude03 on Thursday November 19, 2026 @07:17PM
(#50568464)
Since we’re off topic already - I do have the dxp6800 but I swapped the OS after first boot. Might be worth it to get the hardware but invest in say HexOS or similar
Re:Synology Security Advisory
by devilbunny on Thursday November 19, 2026 @07:41PM
(#50568671)
What did you swap it for? I don't like the direction Synology is going, so my 1621+ is going to be my last one from them (but it's easily got another decade before I think about replacing it), and I'd like to be able to recommend something that's about as easy as Synology and DSM for the technical-but-not-that-technical friends and family.
Re:Synology Security Advisory
by RetroTechie on Thursday November 19, 2026 @07:17PM
(#50568467)
I've always wondered: if you take the cause of each CVE, look at underlying cause of that & repeat, how many essential root problems would you be left with?
"Can't do math" (off-by-1 errors etc)
"Sanitize your inputs" (escape sequences, parsing etc)
"What are you referencing?" (null pointers, use-after-free etc)
and error handling. Plain error codes bubbling up a call stack, or bypassing that somehow which may violate program structure.
Re:Synology Security Advisory
by naasking on Thursday November 19, 2026 @09:12PM
(#50569320)
> I've always wondered: if you take the cause of each CVE, look at underlying cause of that & repeat, how many essential root problems would you be left with?
It's almost always memory safety violations. The rest are basically application-level bugs, like not properly checking inputs.
Re:Synology Security Advisory
by fulafel on Friday November 20, 2026 @01:36AM
(#50570942)
These are all bug classes that are handled by reasonable programming languages since decades ago, so can be reduced to not taking risk management seriously.
Re:Synology Security Advisory
by rtpg on Friday November 20, 2026 @02:13AM
(#50571186)
time of check/time of use issues _might_ be considered "What are you referencing" but the arrow of time feels so important there that I'd consider it its own class
Re:Synology Security Advisory
by wccrawford on Friday November 20, 2026 @09:15AM
(#50574944)
"sanitize your inputs" means you have to know what the output is ahead of time, and that you'll never output any other way. It also means false positives. It can actually be harmful if done wrong (double escaping, escaping that certain systems don't understand) but there's some basic forms that probably aren't too bad. It's generally pointless, though, since...
"escape your outputs" works for all data and is actually achievable. It means even escaping data that was never an "input" from the outside the system, even developer-created data, which absolutely can (and does) cause problems to ignore.
Re:Synology Security Advisory
by edude03 on Thursday November 19, 2026 @07:17PM
(#50568472)
Kind of wild to say there is a critical security vulnerability but the update isn’t out yet. Honestly would have preferred they didn’t tell me until it was patched
Re:Synology Security Advisory
by KiwiJohnno on Friday November 20, 2026 @01:09AM
(#50570779)
Run some flavour of nginx, I used NPM as it has a nice web gui in one container, and run plex in another container. Add reverse proxy rule in NPM to route traffic to plex.
Thats one simple way, another way is to use the built-in synology reverse proxy but... that has also had a vulnerability this week.
I have a DNS wildcard in cloudflare and a more complicated setup with plex on a subdomain, and authelia integrated into NPM to authenticate users before they get through the npm rule.
Re:Synology Security Advisory
by mattbee on Thursday November 19, 2026 @08:37PM
(#50569066)
If you've got an ancient unit like mine where the fix status is "Ongoing" :/ Synology's advised mitigation is to "Remove the OAuth Service Package", i.e. find it from the Package Centre off the main menu, and click Uninstall.
I've never used OAuth, it looked completely unconfigured. But it's the subject of this CVE and seems to be installed by default .
Re:Synology Security Advisory
by madduci on Friday November 20, 2026 @12:06AM
(#50570399)
So they put also some other breaking changes in this upgrade, like offloading the H265 decoding on clients instead of the server. This is very bad taste
Re:Synology Security Advisory
by _rwo on Friday November 20, 2026 @02:29AM
(#50571322)
with the amount of CVEs (self-)hosting becomes a chore tbh; I mean technically it's a good thing that software is getting patched but I think I'm gonna just shutdown few projects (one of which is exposed on Synology's VM via cloudflare tunnel) - I'm getting _patching fatigue_ already
What's your plan for avoiding having attackers find vulnerabilities on Friday, or exploiting them on Saturday/Sunday?
Unplanned is of course unfortunate
It seems pretty improbable that this is a planned release given that when they put out the advisory there wasn't even a patched version available.
EDIT: I just checked and there still isn't a patched release available.
Prepare and parameterize statements you guys.
Nothing gets through the firewall anymore. So now my only vulnerability (I hope) is the firewall, OPNsense.
I've been using Synology for ~12 years, and I've never exposed my NAS to the Internet.
[0]: https://www.wireguard.com/protocol/#dos-mitigation
[1]: https://www.rfc-editor.org/info/rfc4252/#section-5.1
Unfortunately, Synology apps don't support it.
A basic config to set up a VPN that only adds access to services on the VPN itself is very short and simple, both for WireGuard server and for WireGuard clients.
You can run the WireGuard server from your home computer. For example on your NAS machine itself or some other machine you have at home. And open the port for WireGuard to the outside.
Also some routers can run WireGuard server on the router. For example Mikrotik routers have WireGuard server built in and ready to configure [0]. Routers running OpenWrt can too [1].
Or you can rent a small VPS and use that as your WireGuard server.
And then, either which where you run the WireGuard server, run the WireGuard client on your laptops, iOS and Android devices, and connect client apps using VPN internal IP addresses. And your NAS etc too, if the WireGuard server isn’t running on the NAS machine itself.
It really is quite quick to set up with server and all clients across devices.
The only real hurdle is that on iOS you have to turn the VPN back on manually after reboot and which is sometimes easily forgotten if you only use your self hosted services occasionally. But you quickly realize oh right I have to open the WireGuard app and turn on the VPN again whenever you try to use one of your self hosted services and the client isn’t connecting.
[0]: https://manual.mikrotik.com/docs/virtual-private-networks/wi...
[1]: https://openwrt.org/docs/guide-user/services/vpn/wireguard/b...
Generate the config, one per client, setup the client to only route specific RFC1918 networks and disable on well known wifi networks, and that's it. It literally works for years without any maintenance.
Tailscale is easier (presumably), but also puts a corporate entity between you and your data.
I don't work with computers professionally, at all. It still only took me about 2 hours to get the VPS, get Debian going on it, set up headscale, and connect to it from home. Do I still use corporate Tailscale? Yes, it has some features that aren't beautifully supported on headscale, and so for the moment I'm fine with that. But I do have my backup plan in place if I need it.
I have a headscale instance, on one of those $1/mo VPSes, and I don't intend to use it unless I have to. But if I have to, it's there.
You trust yourself with a VPS and correctly configuring a beast such a Debian?
I don't mean to be harsh but even as a professional developer I'm frequently humbled by our grumpy sysadmins on (to me) arcane stuff I didn't knew existed.
They are prime targets and have large attack surface. Even bigger companies are frequently compromised. It's a matter of time before it becomes publicly known.
mTLS is a better option for distributed systems (service to service mesh networks for attestation of workload identities) instead of for human users.
Do I turn on the VPN when I take a picture and turn it off when finished? Every time?
What if I need multiple VPN's? Living in a country that has a bad geoip reputation, it's already a struggle of switching on and off for individual websites to work.
https://github.com/alangrainger/immich-public-proxy/blob/mai...
I have one on-demand VPN with a list of internal IPs to route.
Now if you're going to use mTLS as the basis for mature authn/authz, that's a different story. But I never see anyone do that.
mTLS prevents connecting to the application without valid cert.
Sure the reverse proxy handling the mtls can be exploited, but so can any VPN server as well.
If I told you not to use a power drill as a hammer, you wouldn't claim I'm saying the hammer is at fault for being a bad power drill.
I just take issue (maybe pedantically so) calling it a bad tool and blanket statements that no one uses it for just authn but for authz also. It’s not used for authz. The absence of authz shouldn’t be blamed on mTLS.
Let the family members have their own Linux ISO collections or let them pay streaming scammers.
I am not a big family guy as you can notice. But in my defense no one really cares about my photo albums or ISO files I like.
I personally think Synology are mostly at most fault here though - they shouldn’t be making it so easy for clueless users to do this. It’s basically advertised as a feature.
Very, very few consumer products make it that easy to set up and tie your own noose.
Synology was a perfect solution. Low-cost unit, stick a 15gb drive in it and do again for second unit. DSM is a breeze to work with and the built in rsync was pretty easy to setup and has been working seamlessly for a year now.
Just free willy opening ports and sticking a default setup NAS to the internet, I agree, is asking to be hacked. Tailscale was my preferred way to get them connected but there is no Tailscale Synology client, and if I remember, would required hacks to get one on it and working. Use long passwords for the user is first start. Then on both use the security settings to only accept the ONE IP from each other, even though only one of them is actually exposed to the internet. Also select the settings to install any security updates automatically. Logs show this has all been working good to protect the units. The only catch so far is the IP of his house changed once in the year, being it isn't static, but simply changing it on the sending unit to new one fixed it in about 3 minutes.
I'm thinking of replicating this setup for myself to backup all PC's and phones in my household and syncing to another unit I set up at my relative's house in another state while I visit over the holidays. It pays for itself in short time compared to a cloud provider.
I'm curious now after this CVE how long it will take the units to auto update to newest version after it becomes available to manually install.
The thing even self-updates.
Anyway, I bought one for a client past year, and I won't buy nor recommend one ever again. It's a mess security and technically wise.
They're on a 4.4 kernel (even on recent devices), supposedly backporting security bugfixes. That also means that on a kernel so old you don't have the networking performance improvements and features of the last 10 years.
They're using a btrfs version they forked 10 years ago that they're maintaining out of tree, that also doesn't have any of the new features, and that's not compatible with recent btrfs versions. On top of that, they self built a super messy ACL system that's using a vmtouch version also from 10 years ago.
They always have super outdated libraries. They've been using PHP7.4 (EOLed 4 years ago) until past winter, and PHP8.1 until this summer.
I take a look to the running daemons and... their SMB daemon is based on 4.15.13 (from 2022). Nginx 1.23.1 (from 2022). chrony (it just says DEVELOPMENT version). net-snmp 5.9.3 (2022). rsync 3.1.2 (2015). Postgres 11.11 (2021). Not fun.
And I'm talking about a supported device that got a major OS upgrade this summer.
With this wave of AI security attacks, they don't have much time until something huge appears. Either that, or they use that AI to accelerate going back to mainline versions of the software they use.
--
Synology isn't a panacea (they put themselves in an awkward position with their btrfs fork, with constraints them to stay on an obsolete kernel branch and do a ton of patch shuffling and backporting), but is a much better posture to start homelabing from than, say, a raspbian in a shoebox.
I just recently took a 415+ off the internet (it had Photo Station and Apache only exposed to the outside). I did the "resistor mod" on its JTAG connector to save its Atom from literally frying itself and it's also still working fine. As usual, the hardware far outlives the software.
Does anyone know of any UGREEN UGOS alternatives? I don't mind the terminal but friends prefer a web GUI and for some mundane stuff I too have started to (begrudgingly) prefer it.
"Can't do math" (off-by-1 errors etc)
"Sanitize your inputs" (escape sequences, parsing etc)
"What are you referencing?" (null pointers, use-after-free etc)
and error handling. Plain error codes bubbling up a call stack, or bypassing that somehow which may violate program structure.
How many of these fundamental issues are there?
1. Failure to differentiate data from instructions
2. Business logic flaws
3. Insecure operating environment
4. Incorrect use of cryptography
I mean, I'm kinda kidding, but #1 is #1.
Execute without read is not supported so much though.
Aside from language level enforcement (Java/Rust/...)
It's what still tripping half the people working on security when it comes to LLM.
1. Error that causes security problems
What is being secured (as in, whose interests), and from who?
Security is all nice until one day you find yourself being seen as threat actor. See e.g. all the modern computing devices you "own".
https://top10.owasp.org/2025/
https://community.owasp.org/vulnerabilities/
OWASP already covers this
It's almost always memory safety violations. The rest are basically application-level bugs, like not properly checking inputs.
CVEs are a big deal, but humans are the real vulnerability
I'd phrase that as "know your data access ordering," and include races.
"escape your outputs" works for all data and is actually achievable. It means even escaping data that was never an "input" from the outside the system, even developer-created data, which absolutely can (and does) cause problems to ignore.
Thats one simple way, another way is to use the built-in synology reverse proxy but... that has also had a vulnerability this week.
I have a DNS wildcard in cloudflare and a more complicated setup with plex on a subdomain, and authelia integrated into NPM to authenticate users before they get through the npm rule.
I've never used OAuth, it looked completely unconfigured. But it's the subject of this CVE and seems to be installed by default .
I'm curious if they support mTLS too?
That's never the answer.
Wrong idea: not even a few hours later was it mining bitcoins.
Fortunately only the system partition was affected and I could restore it fully.