dbcve.org
GeocallApplication · Overit

CVE-2019-5891

CRITICAL · 9.8 CVSS v3.1 Published 2019-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An issue was discovered in OverIT Geocall 6.3 before build 2:346977. An unauthenticated servlet allows an attacker to obtain a cookie of an authenticated user, and login to the web application.

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 · high confidence

OverIT Geocall 6.3 contains an unauthenticated servlet that exposes authentication cookies, allowing remote attackers to hijack sessions of legitimate users and gain unauthorized access to the web application.

MitigationUpgrade OverIT Geocall to build 2:346977 or later to patch the vulnerable unauthenticated servlet endpoint.

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
GeocallApplication
Affected:= 6.3

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Geocall version
    Access the application administration panel or check the installation manifest/files for the exact version number of OverIT Geocall
    Affected if The version is reported as exactly 6.3
  2. Locate the web application deployment
    Identify the application server (Tomcat, JBoss, etc.) hosting the Geocall web application and locate the deployed webapp directory
    Affected if The Geocall web application is deployed and accessible over HTTP/HTTPS
  3. Search for unauthenticated servlet endpoints
    Review the application's web.xml deployment descriptor and servlet mappings to identify servlets that do not require authentication
    Affected if A servlet is mapped and accessible without authentication credentials
  4. Test servlet access without credentials
    Attempt to access common servlet paths (such as those ending in /servlet/* or exposed API endpoints) without providing any authentication cookies or session tokens
    Affected if The servlet responds with valid application data or authentication-related information without requiring login
  5. Inspect HTTP responses for cookie exposure
    Capture and examine HTTP responses from the application for Set-Cookie headers containing session tokens or authentication cookies
    Affected if Authentication cookies are returned to unauthenticated requests

A user is affected if OverIT Geocall version 6.3 is installed AND an unauthenticated servlet endpoint is accessible, allowing session cookies to be obtained without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade OverIT Geocall to build 2:346977 or later to patch the vulnerable unauthenticated servlet endpoint.

Recommended fix Moderate confidence

Geocall 6.3 build 2:346977 or later

  1. 1. Identify the current installed build version of Geocall 6.3
  2. 2. Verify if the current build is earlier than build 2:346977
  3. 3. Contact OverIT/QuantumLeap for the patched build (build 2:346977 or later)
  4. 4. Schedule a maintenance window for the upgrade
  5. 5. Back up the current Geocall installation and database
  6. 6. Apply the patched build of Geocall 6.3 (build 2:346977 or later)
  7. 7. Verify the unauthenticated servlet vulnerability is no longer accessible
  8. 8. Test that authentication flows work correctly

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Geocall Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-5891 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-5891 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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