CVE-2019-16245
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 · uneditedOMERO before 5.6.1 makes the details of each user available to all users.
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 confidenceOMERO before version 5.6.1 contains an authorization flaw where user profile details (such as personal information, contact data, or other user-specific attributes) are incorrectly exposed to all authenticated users rather than being restricted to appropriate permissions. This is an information disclosure vulnerability stemming from improper access control on user data endpoints.
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< 5.6.1CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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 installed OMERO server versionRun the command 'omero version' or check the OMERO server package version via your package manager (e.g., dpkg -l | grep omero, rpm -qa | grep omero)Affected if The reported version is earlier than 5.6.1 (for example, 5.6.0, 5.5.x, or any 5.x version below 5.6.1)
-
Confirm OMERO web interface is accessibleVerify the OMERO web client is running and accessible at your OMERO server URL (usually port 8080 or 80/443)Affected if The web interface is active and the version check above shows a vulnerable version
-
Test user data endpoint exposureUsing an authenticated but low-privilege OMERO user account (not admin), attempt to access other user profile endpoints via the OMERO API (e.g., /api/v0/members/ or /api/v0/users/ ) or inspect the JSON response when querying user-related endpointsAffected if A non-admin user can retrieve detailed personal information (email, full name, institution, or other contact data) about other users they should not have access to
You are affected if your OMERO installation version is earlier than 5.6.1 and the web/API interface allows any authenticated user to view other users profile details that should be restricted.
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 data5.6.1
Upgrade OMERO to version 5.6.1 or later, which contains the fix for proper user detail access controls. If immediate upgrade is not possible, review user permission configurations and restrict API access to user detail endpoints.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16245 — 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-16245 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