CVE-2024-50967
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 · uneditedThe /rest/rights/ REST API endpoint in Becon DATAGerry through 2.2.0 contains an Incorrect Access Control vulnerability. An attacker can remotely access this endpoint without authentication, leading to unauthorized disclosure of sensitive information.
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 confidenceThe /rest/rights/ REST API endpoint in Becon DATAGerry through version 2.2.0 lacks proper authentication and authorization controls, allowing unauthenticated remote attackers to access sensitive rights and permissions data.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 DATAGerry installation and versionLocate the DATAGerry installation directory or running service, then check the version file or API (e.g., /rest/info endpoint) to determine the installed version numberAffected if Installed version is 2.2.0 or lower (any version through 2.2.0)
-
Verify the REST API is network-accessibleConfirm that the DATAGerry web interface and REST API ports (commonly 8000 or configured port) are exposed on the network and reachable from untrusted locationsAffected if The API port is accessible from external or untrusted networks
-
Test /rest/rights/ endpoint without authenticationSend an unauthenticated HTTP GET request to http://[datagerry-host]:[port]/rest/rights/ using curl or similar tool, observing the HTTP status code and response bodyAffected if The endpoint returns HTTP 200 with JSON data containing rights/permissions information instead of returning HTTP 401 Unauthorized or HTTP 403 Forbidden
-
Inspect authentication configuration for the endpointReview DATAGerry configuration files (e.g., config files in the installation directory) or API security settings to determine if the /rest/rights/ endpoint has explicit authentication enforcement definedAffected if The endpoint lacks explicit authentication requirements in the configuration
You are affected if running DATAGerry version 2.2.0 or lower AND the /rest/rights/ REST API endpoint returns sensitive rights/permissions data to unauthenticated requests.
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 authentication enforcement and role-based access control (RBAC) on the /rest/rights/ endpoint to ensure only authenticated and properly authorized users can retrieve rights information.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-50967 — 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-2024-50967 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