CVE-2022-50977
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn unauthenticated remote attacker could potentially disrupt operations by switching between multiple configuration presets via HTTP.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn unauthenticated remote attacker can manipulate configuration presets via HTTP requests without proper authorization, allowing them to switch between multiple configuration presets and potentially disrupt system operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify configuration preset endpointsReview your application's routing configuration, API documentation, or web server logs for endpoints related to configuration presets, such as paths containing terms like 'preset', 'config', 'profile', or 'settings'.Affected if The system exposes HTTP endpoints that handle configuration preset operations (load, save, switch, apply).
-
Verify authentication is required for preset modificationsSend an HTTP request to the identified preset endpoints without providing any authentication credentials (no session cookie, API key, or Bearer token). Check the HTTP response code and content.Affected if The request succeeds (2xx status) or returns application data instead of redirecting to a login page or returning 401/403 authentication errors.
-
Confirm authorization checks on preset modification actionsUse a valid authenticated session with a low-privilege or unprivileged user account to attempt modifying configuration presets. Compare the response to determine if the system checks user permissions beyond authentication.Affected if Low-privilege or unauthorized users can successfully modify, switch, or apply configuration presets without receiving 403 Forbidden or permission denied errors.
-
Inspect HTTP method handling for preset endpointsTest various HTTP methods (GET, POST, PUT, DELETE, PATCH) against preset-related endpoints without credentials. Log which methods are accepted and what actions they trigger.Affected if Multiple HTTP methods execute preset changes without requiring authentication or returning proper authorization failures.
Your environment is affected if the system exposes configuration preset management endpoints that accept unauthenticated HTTP requests and allow switching between presets without verifying user authorization.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement proper authentication and authorization checks for all configuration preset modification endpoints, and restrict access to configuration management interfaces to authorized personnel only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-50977 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-50977 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data