Skip to content

GHSA-cqm6-hrgq-6869 CVE-2017-7673

Apache OpenMeetings has Inadequate Encryption Strength

Critical Maven
Severity
9.8 / 10
Critical · CVSS 3.0
Exploit chance (EPSS)
1.65%
Chance of exploitation in the next 30 days. Higher than 76.48% of scored vulnerabilities.
Known exploited
No
Not in CISA's catalog
Weakness
CWE-326 Inadequate Encryption Strength
Fix
3.3.0
Upgrade org.apache.openmeetings:openmeetings-parent to this version or later

Description

Apache OpenMeetings 1.0.0 uses not very strong cryptographic storage, captcha is not used in registration and forget password dialogs and auth forms missing brute force protection.

Affected versions

Maven

PackageVulnerableFixed in
org.apache.openmeetings:openmeetings-parent
>= 1.0.0, < 3.3.0
3.3.0

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

org.apache.openmeetings:openmeetings-parent Maven → 3.3.0

maven
<dependency><groupId>org.apache.openmeetings</groupId><artifactId>openmeetings-parent</artifactId><version>3.3.0</version></dependency>
gradle
implementation("org.apache.openmeetings:openmeetings-parent:3.3.0")

Severity breakdown

CVSS 3.0 9.8

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Weakness

CWE-326: Inadequate Encryption Strength

The product stores or transmits sensitive data using an encryption scheme that is theoretically sound, but is not strong enough for the level of protection required.

How to prevent it
  • Architecture and Design: Use an encryption scheme that is currently considered to be strong by experts in the field.

References

Timeline

  1. Published
  2. Last updated by the source
  3. Latest EPSS score
AdvisorySeverityWhy it's related
GHSA-gcvm-c75m-h4p4
Apache OpenMeetings Uses GET Request Method With Sensitive Query Strings
High Also affects org.apache.openmeetings:openmeetings-parent
GHSA-wqxq-w68r-wg85
Apache OpenMeetings Uses Hard-coded Cryptographic Key
High Also affects org.apache.openmeetings:openmeetings-parent
GHSA-78cg-fc6c-w44w
Apache OpenMeetings has an Improper Handling of Insufficient Privileges vulnerability
Medium Also affects org.apache.openmeetings:openmeetings-parent
GHSA-mjf9-4pcv-vfg7
Apache OpenMeetings vulnerable to Deserialization of Untrusted Data
Critical Also affects org.apache.openmeetings:openmeetings-parent
GHSA-mg5h-f3q8-c96g
Apache OpenMeetings vulnerable to remote code execution via null-bye injection
High Also affects org.apache.openmeetings:openmeetings-parent
GHSA-v9rm-7rv9-r3fw
Apache OpenMeetings Improper Authentication vulnerability
High Also affects org.apache.openmeetings:openmeetings-parent
GHSA-3r48-3m8r-4r9w
Apache OpenMeetings missing authentication and can allow user impersonation
Critical Also affects org.apache.openmeetings:openmeetings-parent
GHSA-pxj9-mw96-q634
Apache OpenMeetings Cross-site Scripting vulnerability
Medium Also affects org.apache.openmeetings:openmeetings-parent
Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor