CVE-2019-5890
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 issue was discovered in OverIT Geocall 6.3 before build 2:346977. Weak authentication and session management allows an authenticated user to obtain access to the Administrative control panel and execute administrative functions.
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 confidenceOverIT Geocall 6.3 before build 2:346977 contains weak authentication and session management that allows an authenticated user to escalate privileges and access the Administrative control panel, executing administrative functions beyond their authorized scope.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 6.3CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 the installed OverIT Geocall versionAccess the application or system where Geocall is installed. Look for version information in the application itself (typically in About, Help, or Version pages), check installation logs, or query the application's internal version reporting. Compare this version to the affected range (6.3).Affected if The installed version is exactly 6.3 or falls within the 6.3 release line before the patch was applied.
-
Determine the build number of the installationLocate the specific build identifier for the Geocall installation. This may be visible in the application's system information, within configuration files, or in the database metadata where build information is stored. The vendor specifically references build 2:346977 as the patched version.Affected if The build number is before 2:346977, indicating the vendor patch has not been applied.
-
Inspect session token implementationExamine how the application handles session tokens. Review session cookie configuration, token generation methods, and session persistence mechanisms. Look for whether session tokens are predictable, lack proper randomness, or can be reused across authentication cycles.Affected if Session tokens exhibit weakness such as predictability, insufficient entropy, or lack of proper validation on each request.
-
Review role-based access control enforcementTest or inspect whether the application properly enforces role boundaries. This includes verifying that standard users cannot access administrative functions, and that privilege escalation attempts are properly blocked at the application layer.Affected if The application permits authenticated users to access administrative functions beyond their authorized role scope, indicating broken access controls.
If the installed OverIT Geocall version is 6.3 with a build number earlier than 2:346977, the environment contains the authentication and session management weaknesses described in this CVE.
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 dataUpgrade to build 2:346977 or later to obtain the vendor patch addressing authentication and session management weaknesses; implement proper session token validation and enforce role-based access controls.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-5890 — 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-2019-5890 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