GHSA-97jg-43c9-q6pf CVE-2022-24819
Unauthenticated user can retrieve the list of users through uorgsuggest.vm
Medium
Maven
- Severity
- 5.3 / 10
- Medium · CVSS 3.1
- Exploit chance (EPSS)
- 3.20%
- Chance of exploitation in the next 30 days. Higher than 88.12% of scored vulnerabilities.
- Known exploited
- No
- Not in CISA's catalog
- Weakness
- CWE-359 Exposure of Private Personal Information to an Unauthorized Actor
- Fix
12.10.11- Upgrade org.xwiki.platform:xwiki-platform-web-templates to this version or later
Description
A guest user without the right to view pages of the wiki can still list documents related to users of the wiki. The problem has been patched in XWiki versions 12.10.11, 13.4.4, and 13.9-rc-1. There is no known workaround for this problem.
Affected versions
Maven
| Package | Vulnerable | Fixed in |
|---|---|---|
| org.xwiki.platform:xwiki-platform-web-templates | < 12.10.11 |
12.10.11 |
| org.xwiki.platform:xwiki-platform-web-templates | >= 13.0.0, < 13.4.4 |
13.4.4 |
| org.xwiki.platform:xwiki-platform-web-templates | >= 13.5.0, < 13.9 |
13.9 |
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.xwiki.platform:xwiki-platform-web-templates Maven → 12.10.11
- maven
<dependency><groupId>org.xwiki.platform</groupId><artifactId>xwiki-platform-web-templates</artifactId><version>12.10.11</version></dependency>- gradle
implementation("org.xwiki.platform:xwiki-platform-web-templates:12.10.11")
Severity breakdown
CVSS 3.1 5.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
Weakness
CWE-359: Exposure of Private Personal Information to an Unauthorized Actor
The product does not properly prevent a person's private, personal information from being accessed by actors who either (1) are not explicitly authorized to access the information or (2) do not have the implicit consent of the person about whom the information is collected.
How to prevent it
- Requirements: Identify and consult all relevant regulations for personal privacy. An organization may be required to comply with certain federal and state regulations, depending on its location, the type of business it conducts, and the nature of any private data it handles. Regulations may include Safe Harbor Privacy Framework [REF-340], Gramm-Leach Bliley Act (GLBA) [REF-341], Health Insurance Portability and Accountability Act (HIPAA) [REF-342], General Data Protection Regulation (GDPR) [REF-1047], California Consumer Privacy Act (CCPA) [REF-1048], and others.
- Architecture and Design: Carefully evaluate how secure design may interfere with privacy, and vice versa. Security and privacy concerns often seem to compete with each other. From a security perspective, all important operations should be recorded so that any anomalous activity can later be identified. However, when private data is involved, this practice can in fact create risk. Although there are many ways in which private data can be handled unsafely, a common risk stems from misplaced trust. Programmers often trust the operating environment in which a program runs, and therefore believe that it is acceptable store private information on the file system, in the registry, or in other locally-controlled resources. However, even if access to certain resources is restricted, this does not guarantee that the individuals who do have access can be trusted.
- Implementation, Operation: Some tools can automatically analyze documents to redact, strip, or "sanitize" private information, although some human review might be necessary. Tools may vary in terms of which document formats can be processed. When calling an external program to automatically generate or convert documents, invoke the program with any available options that avoid generating sensitive metadata. Some formats have well-defined fields that could contain private data, such as Exchangeable image file format (Exif), which can contain potentially sensitive metadata such as geolocation, date, and time [REF-1515] [REF-1516].
References
Advisories
Packages
Other links
Timeline
- Published
- Last updated by the source
- Latest EPSS score
Related advisories
| Advisory | Severity | Why it's related |
|---|---|---|
| GHSA-w4fj-87j5-f25c XWiki has Reflected Cross-Site Scripting (XSS) in page history compare | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-wvqx-m5px-6cmp XWiki Affected by Reflected Cross-Site Scripting (XSS) in Error Messages | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-7vpr-jm38-wr7w XWiki vulnerable to a reflected XSS via xredirect parameter in DeleteApplication | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-m9x4-w7p9-mxhx XWiki allows Reflected XSS in two templates | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-f963-4cq8-2gw7 In XWiki Platform, payloads stored in content is executed when a user with script/programming right edit them | High | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-692v-783f-mg8x XWiki Platform vulnerable to Cross-Site Scripting (XSS) through conflict resolution | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-93gh-jgjj-r929 XWiki Platform vulnerable to XSS with edit right in the create document form for existing pages | Medium | Also affects org.xwiki.platform:xwiki-platform-web-templates |
| GHSA-qcj9-gcpg-4w2w XWiki Platform web templates vulnerable to reflected XSS in the create document form if name validation is enabled | Critical | Also affects org.xwiki.platform:xwiki-platform-web-templates |
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