mirror of
https://github.com/louislam/uptime-kuma.git
synced 2026-03-02 22:57:00 -05:00
Incorrect accepted_statuscodes via API (using python uptime-kuma-api package) made kuma completely non-functional #2437
Labels
No labels
A:accessibility
A:api
A:cert-expiry
A:core
A:dashboard
A:deployment
A:documentation
A:domain expiry
A:incidents
A:maintenance
A:metrics
A:monitor
A:notifications
A:reports
A:settings
A:status-page
A:ui/ux
A:user-management
Stale
ai-slop
blocked
blocked-upstream
bug
cannot-reproduce
dependencies
discussion
duplicate
feature-request
feature-request
good first issue
hacktoberfest
help
help wanted
house keeping
invalid
invalid-format
invalid-format
question
releaseblocker 🚨
security
spam
type:enhance-existing
type:new
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/uptime-kuma#2437
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
Originally created by @mgaller on GitHub (Aug 3, 2023).
⚠️ Please verify that this bug has NOT been raised before.
🛡️ Security Policy
Description
Passing incorrect input [200] to accepted_statuscodes via the python api package made kuma completely non-functional.
The backend should do atleast some validation on fields, before saving monitors.
👟 Reproduction steps
Create a Monitor via the Python API using "uptime-kuma-api"
👀 Expected behavior
Throwing some sort of error and not saving the incorrect monitor.
😓 Actual Behavior
Server crashes directly and on every startup, can not reach Backend or use the API.
🐻 Uptime-Kuma Version
1.22.1 with docker alpine
💻 Operating System and Arch
Ubuntu 22.04.2 LTS
🌐 Browser
Firefox 115
🐋 Docker Version
Docker version 24.0.5
🟩 NodeJS Version
16
📝 Relevant log output
@CommanderStorm commented on GitHub (Aug 3, 2023):
We don't have an api, nor do we maintain the package you are using.
See #118 for further information.
Please raise the issue here https://github.com/lucasheld/uptime-kuma-api