r/linuxadmin • • 35m ago

SAP November 2026 Patch Day: Four CVSS 10.0 vulnerabilities across ICM, Web Dispatcher, Gateway and SAML2

0 Upvotes

Based on SAP's November 10 security bulletin, Onapsis Research Labs' ICM2SHELL analysis and the Cyber Security Agency of Singapore's November 16 advisory, four SAP vulnerabilities deserve attention across different enterprise trust boundaries.

The technical split is important:

  • CVE-2026-76964: Memory corruption in SAP NetWeaver Internet Communication Manager.

  • CVE-2026-89126: Memory corruption in SAP Web Dispatcher. Onapsis connects this to shared WebSocket-handling code and identifies the issue as ICM2SHELL.

  • CVE-2026-89103: Broken access control in SAP Gateway.

  • CVE-2026-120017: Missing authentication in the SAML2 Service Provider.

The first two are particularly interesting from an infrastructure perspective. Web Dispatcher can be the reverse proxy sitting at the edge of an SAP landscape, while the ICM handles HTTP/HTTPS communication. A weakness in shared kernel-level traffic handling means both components need individual inventory and patch verification.

The Gateway issue raises a different question: how much does the application trust a system simply because it can reach the Gateway?

The SAML2 vulnerability adds an identity boundary problem. Authentication assertions must be validated correctly; otherwise, the service provider may accept an identity that should never have been trusted.

For defenders, I would prioritize:

  1. Inventory internet-facing ICM and Web Dispatcher instances.

  2. Verify SAP Security Notes 3778530, 3778556, 3798345 and 3849308 against installed component levels.

  3. Review Gateway access-control configuration, including secinfo/reginfo.

  4. Inspect SAML2 authentication events and privileged account activity.

  5. Correlate SAP logs, reverse-proxy requests, firewall flows and operating-system process telemetry.

One qualification: a CVSS 10.0 score does not establish active exploitation. Onapsis stated that it had not observed in-the-wild exploitation of ICM2SHELL as of its November 12 update.

https://www.techgines.com/post/sap-netweaver-vulnerabilities-four-cvss-10-0-flaws-explained

Technical sources:

Historical context: Cisco IMC Authentication Bypass CVE-2026-20093

For teams running large SAP landscapes: do you enforce Gateway-level trust controls independently of network segmentation, or does reachability still imply trust in your deployments?


r/linuxadmin • • 23h ago

Nova compute is down and inaccessible via SSH. What would you instigate first and fix?

0 Upvotes

In my project, i have observed that one of the compute reporting as down.

I have checked ilo console of the server (hpe vendor), everything looks good there.

SSH isn't working and throwing no route to host error.

Need help to fix.


r/linuxadmin • • 1d ago

GitHub - danielecr/tetragon-outgoing-guard: block any process with outgoing connection (run only on k8s or docker swarm vms)

Thumbnail
github.com
6 Upvotes

How I locked down my Docker host against GSocket-style C2 implants using a 50-line Cilium Tetragon eBPF policy.

Also in docker swarm, I mean, the only services are supposed to be in container


r/linuxadmin • • 1d ago

No syslog during the outage = a stalled support case. I built a free syslog server to fix that part

0 Upvotes

I work escalations for network gear. The cases that stall the longest usually look the same: the outage happened, the device rebooted or rolled its buffer, and there's no syslog from the window that matters. Either nobody had a syslog server, or the one they had dropped messages and nobody knew. At that point the best anyone can do is "set up logging and wait for it to happen again", and the case just sits.

A lot of the time it's not that people don't know syslog. It's that the box available is a Windows server or a laptop, and standing up something reliable there takes longer than it should. Woodshed is my answer to that: MSI, pkg, deb, rpm or a portable zip. Listens on UDP and TCP 514 straight away. Plain text files per device per day, a disk budget it won't exceed, drop/refused counters shown in the UI, and an export zip with a manifest, SHA-256s and the gaps when it wasn't running, so the person on the other end of the case can trust it.

Most of the code was written with AI assistance. I did the design and ran the lab testing; the security review was a separate AI reviewer with read-only access to the code, and I went through every finding, decided the fixes and had them re-tested.

All the testing so far is lab traffic generated by my own sender (RFC 5424, RFC 3164 and bare lines, 8 source IPs). No real devices yet beyond a friend's homelab, which is in progress. It doesn't depend on any vendor's format and always keeps the raw line exactly as received, so any device that speaks syslog should work, but I haven't proven that.

What it's been through:

- release bench every tag: 10 min at 10k msg/s UDP on a 4 vCPU GitHub runner, 6,000,000 sent / 6,000,000 stored / 0 missing

- Ubuntu 24.04 (deb) and AlmaLinux 9 (rpm) VMs, 8 senders over a real network: 0 loss to 40k msg/s TCP at ~1/3 of a core and <50 MiB RSS. UDP loss above that was before the VM's NIC (interface counters), every datagram that arrived was stored

- reboot mid-stream: service back on its own, 2 UDP messages lost, export shows the 17-19 s gap as "Woodshed wasn't running"

- 24 h soak at 3,000 msg/s on the Linux VMs, 259.2M messages each: TCP exactly once, UDP lost 3-4 per million, all of it upstream of the VM

- security review before the first RC: 0 critical, 1 high (memory exhaustion from spoofed sources), 7 medium. fixed and re-tested twice

- CI install/upgrade/uninstall on Windows, macOS and Linux, x64 and ARM. checksums + `gh attestation verify` on releases

Limits, plainly:

- unsigned installers for now. SmartScreen ("Windows protected your PC", More info > Run anyway) and Gatekeeper (Privacy & Security > Open Anyway) ask once

- 1.0.0

- use the sender allowlist on untrusted segments. in my lab an open 514 on a shared /16 collected a stranger's syslog within minutes

- not a SIEM, no TLS syslog/alerts/forwarding yet

- Windows and macOS don't expose kernel UDP drops, the UI says so instead of showing 0

What I'd like to know:

  1. Which devices or formats break the parser? Redacted raw line please.

  2. What would you need to see before you'd drop this at a customer site during an outage?

  3. Windows folks, especially with endpoint protection: did it get flagged, did the firewall rules behave?

Repo: https://github.com/gmccollu/woodshed

Site: https://gmccollu.github.io/woodshed/

Releases: https://github.com/gmccollu/woodshed/releases


r/linuxadmin • • 1d ago Bravo

Linux server has high load average but low CPU usage. What would you investigate first?

64 Upvotes

I'd like to discuss a Linux troubleshooting scenario and get some input from experienced Linux administrators.

Imagine you're troubleshooting a production Linux server with the following symptoms:

  • Application response time is increasing.

  • Load average is continuously rising.

  • CPU utilization is only around 20–25%.

  • Several application processes are stuck in D state.

  • The application uses an NFS-mounted directory.

At first glance, CPU doesn't seem to be the bottleneck.

If you were handling this incident, how would you approach the investigation?

A few things I'd be interested in discussing:

  1. Would you start with vmstat to check runnable and blocked processes?

  2. How would you identify what the D-state processes are waiting for?

  3. What commands would you use to investigate NFS connectivity and mount health?

  4. How would you distinguish an NFS issue from local disk I/O problems?

I'm particularly interested in real production experiences.

Have you encountered a similar situation? What was the root cause, and what helped you identify it?

Looking forward to learning from your experiences.


r/linuxadmin • • 2d ago

Apache CVE-2026-119618 (CVSS 9.8, mod_http2 RCE): quick check + mitigation if your distro hasn't shipped 2.4.71 yet

23 Upvotes

Apache 2.4.71 fixes a race condition in mod_http2 (assign_headers) that can corrupt the heap and allow unauthenticated RCE. Affected: 2.4.55 – 2.4.70, only if HTTP/2 is enabled.

Quick check:

apachectl -v

apachectl -M | grep -i http2

curl -so /dev/null -w '%{http_version}\n' --http2 https://your-site.com/

If curl prints 2, you're exposed.

Patch status as of Nov 12:

- Debian 13: fixed (2.4.71-1~deb13u1)

- RHEL 9/10: fixed via updated mod_http2

- Ubuntu 24.04 / 26.04: affected, no USN yet

- Ubuntu 22.04 (2.4.52): not in range

No patch yet? Disable HTTP/2 until you can:

sudo a2dismod http2

# set "Protocols http/1.1" in any vhost that lists h2

sudo apachectl configtest

sudo systemctl restart apache2

On RHEL-family systems, comment out LoadModule http2_module in /etc/httpd/conf.modules.d/10-h2.conf.

Note: some distros backport the fix without bumping the version, so check your security tracker, not just the version number.

I wrote a longer version with a per-distro table and FAQ here: https://arelvox.com/apache-cve-2026-119618-http2-rce/


r/linuxadmin • • 2d ago

Considering a career switch from Video Editing to Linux System Administration. Is it worth it?

22 Upvotes

I'm currently working as a Video Editor with around 2 years and 10 months of experience. I have a B.E. in Computer Science and Engineering.

Over time, I've lost interest in video editing and have become increasingly interested in Linux, servers, system administration and infrastructure.

I've been experimenting with Arch Linux, Oracle Cloud, SSH, home servers, Docker and self-hosting. I genuinely enjoy troubleshooting and understanding how systems work.

I'm considering starting over in Linux System Administration, eventually exploring Cloud or DevOps.

A few questions:

  • Is this a sensible career switch?

  • How difficult is it to get an entry-level Linux job without professional IT experience?

  • What are the long-term salary and career prospects in India?

  • Is system administration still a good career in the age of AI and automation?

I'm currently earning around ₹35k/month, so I have financial responsibilities and cannot afford to start completely from zero.

Would you recommend making this transition? I'd appreciate honest advice, especially from people working in Linux/System Administration.


r/linuxadmin • • 2d ago

A modern reverse proxy built for dynamic infrastructure.

Post image
0 Upvotes

I've been working on Aralez, an open-source reverse proxy and load balancer written in Rust, built on top of Cloudflare's Pingora.

The project started as an attempt to build a performant, flexible proxy that could handle more than basic HTTP load balancing. Over time, it has grown into a fairly feature-rich system.

Some of the new features implemented in the latest v0.95.5 release

  • Response Caching: With Memory, Hybrid, RESP (Redis family), TiKV storages

  • Cluster Mode: Master/worker deployment model.

  • Structured logging: Plug-able modules, currently Elasticsearch.

  • Acme DNS-01 Challenge: Plugable currently Cloudflare, Route 53, DigitalOcean

  • The full list of features are here

I'm particularly interested in feedback from people with experience in Rust networking, asynchronous systems, proxies and high-performance services.

Also would be very thankful for code contribution, especially with Acme DNS-01 providers.

Examples are at the bottom this page.

GitHub: https://github.com/sadoyan/aralez
Documentation: https://aralez.rs/


r/linuxadmin • • 3d ago

VyOS after 36 days remembers about critical CVE-2026-98432 .

0 Upvotes

Because they've carried some weird patch; it is unclear if this actually resolves the problem based on their bad track record on backporting.


r/linuxadmin • • 3d ago

fail2ban kept "banning" IPs that kept hammering my Docker ports — the bans were landing in the wrong iptables chain

0 Upvotes
Spent days wondering why fail2ban kept banning IPs that kept hammering my Docker-published WordPress login. The bans were inserted, "fail2ban-client status" said banned — but the traffic never stopped.

The reason: on a Docker host, fail2ban's default action drops rules into the INPUT chain. Packets to published ports are processed by Docker's FORWARD/DOCKER-USER chain *before* INPUT sees them. So the ban is real, it just drops nothing.

The fix is one token — point the action at DOCKER-USER:

    [igornews-wp]
    enabled   = true
    filter    = igornews-wp
    logpath   = /opt/igornews/logs/access.log
    action    = iptables[type=allports, chain=DOCKER-USER, blocktype=DROP]
    bantime   = 1h
    findtime  = 10m
    maxretry  = 6

Second gotcha in the same jail: it reads Caddy's JSON access log, whose timestamp is a fractional epoch mid-line, so I needed a custom datepattern = "ts":{LEPOCH} or fail2ban parsed zero lines.

The verify step that would've caught this in five minutes: after a ban, run "iptables -L DOCKER-USER -n" and actually see the IP there — never trust "fail2ban is running."

Full walk-through with the JSON-log filter regex: https://igornews.com/2026/11/08/fail2ban-docker-user-chain-bans/

r/linuxadmin • • 3d ago

Critical vulnerability in Apache with HTTP2 module enabled

Thumbnail nvd.nist.gov
31 Upvotes

r/linuxadmin • • 4d ago

QA for xcp-hl

Thumbnail
reddit.com
2 Upvotes

r/linuxadmin • • 4d ago

Det Mimir update: clearer explanations, sample investigations and the roadmap

Thumbnail
gallery
0 Upvotes

Hey guys o/

First and foremost, thank you for taking the time to read through the post :)

I posted here previously about Det Mimir, the read-only Linux incident investigation engine I’m building:
Previous post

I’ve just redesigned the website, based on feedback I’ve collected over the past few weeks, with readability and clearer product explanations as the main priorities.

The updated site: https://det-mimir.com/

For anyone coming across it for the first time, these are the main things I’m building around:

  • Scoped investigations: start from a failing service, restarting container, disk pressure or another supported symptom, with a defined time window.

  • Traceable findings: evidence from different sources is correlated into a timeline and report. You can follow findings back to their records and see where missing evidence limits the assessment.

  • Deterministic analysis: the investigation engine works without an LLM. AI analysis is an optional step afterwards.

  • Read-only collection: commands come from a vetted registry. No arbitrary shell execution, automatic repairs or model-triggered commands.

  • Control over your data: evidence and reports stay local. No telemetry or phone-home. Optional external-model analysis uses sanitized context, a send preview and an approved sending path.

There’s also a security investigation direction: the Exploit Evidence Pack, currently in development. It’s intended to correlate offline vulnerability intelligence with host evidence to assess whether there are signs of exploitation. A vulnerable software version alone would not establish that exploitation happened.

The public roadmap explains the broader direction too, including multi-host coordination, more integrations, and the longer-term investigation-pack ecosystem.

Roadmap:
https://det-mimir.com/roadmap/

Det Mimir remains in private validation, and I'm also validating beta users ;)

The website now has clearer diagrams and readable sample reports, so you can inspect what an investigation actually produces.

I’d really appreciate you taking a look :) Does it explain the product clearly, and can you see where it would, or wouldn’t, help in your own investigations?


r/linuxadmin • • 4d ago

SSHole (CVE-2026-123158) is in CISA KEV: if you run Alpine with sshd, update openssh and restart sshd. Here's who's actually affected

0 Upvotes

Quick rundown, since the affected set is narrow but very real. The bug needs sshd built and run without PAM on musl libc. On Alpine, that's the default `openssh-server` package, or `openssh-server-pam` with `UsePAM no`. `PasswordAuthentication` also has to be on, which is the default. Then the box needs an account whose shadow field is `*` (key-only users, directory users via musl-nscd, and root on images since about 3.16), plus at least one account with a `$5$` or `$6$` hash. An attacker sends a 257 to 1024 byte password and gets in on the first try. musl's crypt() returns `*` as its error string for keys over 256 bytes, and that matches the stored field. Root itself is still protected by the default `PermitRootLogin prohibit-password`, but any other passwordless account that can doas to root is enough.

Fix: `apk upgrade -U -a`, then `rc-service sshd restart`, because the running daemon keeps the old code until you restart it. Fixed builds are openssh 10.6_p2-r0 on edge, 10.3_p1-r2 on 3.24, 10.2_p1-r1 on 3.23, 10.0_p1-r11 on 3.22 and 9.9_p2-r1 on 3.21, and Alpine also pushed fixes for 3.16 to 3.20. If you can't update yet, `PasswordAuthentication no` closes it. Run `sshd -T | grep -i passwordauthentication` afterwards to confirm, and keep your current session open while you test a new key login. Watch out for the official tiny-cloud images (qcow2, VHD, AMI, 3.18.11 through 3.24.3). They ship an `alpine` user with no password and passwordless doas, so they become exploitable the moment anyone sets a console password. Cloud-init images are fine because cloud-init writes `PasswordAuthentication no`.

If an exposed box had password auth on, check `/var/log/messages` for "Accepted password for" on an account that has no password, and look at recent users, authorized_keys and doas use. Debian and Ubuntu aren't in the same position. Debian's tracker rates it "unimportant" (stable packages are still listed as vulnerable, with the fix only in sid/forky so far), and Ubuntu's note says it doesn't use musl by default. So I'd still put the update on the list there, but it's not an emergency.

Two other Linux services joined KEV the same day, and both have had fixes for a while: GPUStack (2.2.0, advisory from Jul 31) and FreeSWITCH (1.11.3, advisory from Oct 28). CISA confirmed exploitation of both this week.

Alpine advisory: https://alpinelinux.org/posts/2026-11-05-openssh-password-authentication-bypass/
Debian tracker: https://security-tracker.debian.org/tracker/CVE-2026-123158
Fixed versions for the rest of this week's KEV list: https://patchorpass.beehiiv.com/?utm_source=reddit&utm_medium=social&utm_campaign=issue-4&utm_content=linuxadmin


r/linuxadmin • • 5d ago

tips for optimizing apache server on a low resource vm

7 Upvotes

I've been running an apache server on a low resource vm and it's been kinda sluggish lately. anyone got tips on what modules to disable or tweaks to make for better performance? I've looked into things like changing the KeepAlive settings and maybe lowering MaxClients, but not sure if that's enough. would love to hear what other configs you guys have found helpful in similar situations.


r/linuxadmin • • 5d ago

ldapbrowser v1.2.0: interactive LDAP/AD browser in pure bash+curl+fzf, now with log management and concurrent instances

Post image
39 Upvotes

I’m the author. ldapbrowser is a read-only LDAP/AD directory browser for the terminal.
It needs only bash, curl and fzf, so it can run on jump servers easily.

New in v1.2.0 release:

  • CA certificate chosen with an fzf file picker during setup

  • log view/show/clean

  • Multiple instances can run in parallel, each with its own temp directory

  • TERM/HUP/EXIT signal handling

  • Better dependency check and detailed help for the directory types in setup

  • Detailed LDAP directories vendors references

Tested against 10 directory implementations: AD, FreeIPA, OpenLDAP, 389 DS, OpenDJ, ApacheDS, Okta, OneLogin VLDAP, JumpCloud and FoxPassOkta. It is read-only by design.

The code is written and tested by hand. I used AI only to help draft the README and CHANGELOG.

github.com/mytechspacexyz/ldapbrowser


r/linuxadmin • • 6d ago

Monitoring Updates [Debian / Red Hat]

Thumbnail
reddit.com
1 Upvotes

r/linuxadmin • • 6d ago

How do you rotate an API key that's in the monitoring agent's config on every host?

0 Upvotes

Push a new key and any host that missed the change stops reporting, but keep both valid and the old one never gets turned off, because nobody knows who still uses it. Elastic Agent avoids this: each host enrolls with a token, then gets its own API key. Do you accept the gap, overlap the keys, or issue per-host keys?


r/linuxadmin • • 6d ago

CVE-2026-123158 (“sshole”): OpenSSH password bypass through musl crypt() error handling

0 Upvotes

Based on the OpenSSH 10.6p2 release notes and Alpine Linux's technical advisory, CVE-2026-123158 is a narrowly scoped password-authentication bypass affecting certain Linux OpenSSH builds using musl without PAM.

The interesting part is the comparison logic.

In the affected non-PAM authentication path, sshd uses crypt() to verify a candidate password. Alpine documents a case where an account has * in its shadow password field, while another local account has a $5$ or $6$ hash. The implementation can borrow a salt from that other account. For an overlong password, musl can return * as an error indicator. The comparison can then treat that error value as a match for the stored *.

The affected configuration requires more than just running OpenSSH:

  • An affected musl-based build without PAM, or a PAM build configured with UsePAM no.

  • PasswordAuthentication yes.

  • A local account with * in its shadow field.

  • At least one other local $5$ or $6$ password hash.

Alpine lists fixed packages across its supported branches. The upstream mitigation is in OpenSSH 10.6p2. Alpine also notes that upgrading the package is not enough if the running daemon has not been restarted.

Operationally, I would inventory the sshd build, libc and effective configuration, then correlate successful Accepted password for events with an explicit list of accounts meant to be key-only. A successful password login to such an account is worth investigating, but it is not proof of exploitation without confirming the host's affected conditions.

Primary sources:

TechGines technical breakdown: https://www.techgines.com/post/openssh-password-authentication-bypass-cve-2026-123158

For fleets with mixed Alpine and non-Alpine hosts, how are you tracking the combination of libc, SSH build options, PAM settings and shadow-file account state? Is that inventory already queryable alongside authentication events, or is it still a manual audit?