starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

User without sufficient permission can create an IP address via FHRP group creation #7145

New Issue
Closed
opened 2025-12-29 20:19:42 +01:00 by adam · 1 comment
adam commented 2025-12-29 20:19:42 +01:00
Owner
Copy Link

Originally created by @jeremystretch on GitHub (Oct 21, 2022).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.3.5

Python version

3.8

Steps to Reproduce

  1. Create a user with permission to view and create FHRP groups but not IP addresses.
  2. Authenticate as that user.
  3. Create an FHRP group with any valid values, and also specify an IP address and status.

Expected Behavior

The creation of an IP address should not be permitted, as the user lacks sufficient permissions.

Observed Behavior

The IP address is created.

Originally created by @jeremystretch on GitHub (Oct 21, 2022). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.3.5 ### Python version 3.8 ### Steps to Reproduce 1. Create a user with permission to view and create FHRP groups but not IP addresses. 2. Authenticate as that user. 3. Create an FHRP group with any valid values, and also specify an IP address and status. ### Expected Behavior The creation of an IP address should not be permitted, as the user lacks sufficient permissions. ### Observed Behavior The IP address is created.
adam added the type: bugstatus: accepted labels 2025-12-29 20:19:42 +01:00
adam closed this issue 2025-12-29 20:19:42 +01:00
adam commented 2025-12-29 20:19:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 26, 2022):

To be clear, @arthanson's approach in #10747 is greatly preferred over my hack. However, as noted in the PR adding a new method to a generic view would technically be a breaking change to the plugins API, so we'll have to defer for now.

@jeremystretch commented on GitHub (Oct 26, 2022): To be clear, @arthanson's approach in #10747 is greatly preferred over my hack. However, as noted in the PR adding a new method to a generic view would technically be a breaking change to the plugins API, so we'll have to defer for now.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#7145
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?