SVI/netbird
1
0
Fork 0
mirror of https://github.com/netbirdio/netbird.git synced 2026-07-24 15:03:59 -04:00
Code Issues 3.0k Packages Projects Releases 10 Wiki Activity

Unexpected SSH access to routing peer despite non-existent policy #2445

New Issue
Closed
opened 2025-11-20 07:09:56 -05:00 by saavagebueno · 0 comments
saavagebueno commented 2025-11-20 07:09:56 -05:00
Owner
Copy Link

Originally created by @CodingTil on GitHub (Nov 7, 2025).

Describe the problem

SSH access to network routing peers is permitted via netbird ssh despite no policy explicitly allowing access between the relevant groups/peers.

To Reproduce

Steps to reproduce the behavior:

  1. Create a Peer (for routing)
  • Name: "exit_node"
  • Group: "Exit Node"
  • Enable SSH Access (also when starting the client on that machine)
  1. Create a Network, e.g.:
  • Name: Public Internet
  • Network Resource:
    • Name: "Internet"
    • Group: "Internet"
    • CIDR: 0.0.0.0/0
  • Network Routing Peer:
    • Group: "Exit Node"
  1. Create a Policy:
  • Name: "All to Internet"
  • From: Group "All" (doesn't matter, just make sure u are in this group)
  • To: Group "Internet" (this contains the Network Resource, but not the Network Routing Peer)
  1. Connect to the exit node:
  • sudo netbird ssh root@exit_node
  • The connection works.

Expected behavior

One cannot connect, as there is no rule that allows traffic addressed to the Peer "exit_node".

Are you using NetBird Cloud?

Self-Hosted

NetBird version

0.59.11 (Server)

Is any other VPN software installed?

No

Debug output

I don't believe this is necessary.

Screenshots

I don't believe this is necessary.

Additional context

Add any other context about the problem here.

Have you tried these troubleshooting steps?

  • Reviewed client troubleshooting (if applicable)
  • Checked for newer NetBird versions
    • The changelog for 0.59.12 does not imply this was fixed.
  • Searched for similar issues on GitHub (including closed ones)
  • Restarted the NetBird client
  • Disabled other VPN software
  • Checked firewall settings
Originally created by @CodingTil on GitHub (Nov 7, 2025). **Describe the problem** SSH access to network routing peers is permitted via netbird ssh despite no policy explicitly allowing access between the relevant groups/peers. **To Reproduce** Steps to reproduce the behavior: 1. Create a Peer (for routing) - Name: "exit_node" - Group: "Exit Node" - Enable SSH Access (also when starting the client on that machine) 2. Create a Network, e.g.: - Name: Public Internet - Network Resource: - Name: "Internet" - Group: "Internet" - CIDR: 0.0.0.0/0 - Network Routing Peer: - Group: "Exit Node" 3. Create a Policy: - Name: "All to Internet" - From: Group "All" (doesn't matter, just make sure u are in this group) - To: Group "Internet" (this contains the Network Resource, but not the Network Routing Peer) 4. Connect to the exit node: - `sudo netbird ssh root@exit_node` - The connection works. **Expected behavior** One cannot connect, as there is no rule that allows traffic addressed to the Peer "exit_node". **Are you using NetBird Cloud?** Self-Hosted **NetBird version** 0.59.11 (Server) **Is any other VPN software installed?** No **Debug output** _I don't believe this is necessary._ **Screenshots** _I don't believe this is necessary._ **Additional context** Add any other context about the problem here. **Have you tried these troubleshooting steps?** - [X] Reviewed [client troubleshooting](https://docs.netbird.io/how-to/troubleshooting-client) (if applicable) - [X] Checked for newer NetBird versions - The changelog for 0.59.12 does not imply this was fixed. - [X] Searched for similar issues on GitHub (including closed ones) - [X] Restarted the NetBird client - [X] Disabled other VPN software - [X] Checked firewall settings
saavagebueno added the triage-needed label 2025-11-20 07:09:56 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
2021 Q4
2022 Q1
2022 Q1
accessibility
acl
agent
agent
Android
Android
api
authentik
automation
azure
battery-usage
bug
cache
client
client-ui
cloud
cloud-only
cloudflare
community
compatibility
config-idp
config-issue
connection
contribution
coturn
cross-vpn
dashboard
data-usage
distribution
dns
docker
documentation
duplicate
enhancement
enhancement
event-stream
feature-request
freebsd
getting-started
go
good first issue
gui
help wanted
home-assistant
idp
inconsistency
integration
integrations
ios
ipv6
jwt
k8s
keycloak
linux
login
macos
management-service
missing-docs
mobile
moved-internal
needs-review
netbird-ui
networking
new-platform
nginx
notification
okta
openwrt
packaging
peer-management
peer-management
peer-management
performance
postgres
posture-checks
psk
pull-request
Mirrored from GitHub Pull Request
 question
refactor
relay
release
rfc
routes
security
security-related
self-hosting
server
signal
sleep-issue
ssh
ssl
status
store
synology
system-compatibility-issue
test-suite
third-party-integration
triage
triage-needed
troubleshooting
UX
waiting-feedback
windows
wontfix
zitadel
No Label triage-needed
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/netbird#2445
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?