Skip to content

docconv vulnerable to Memory Allocation with Excessive Size Value

Moderate severity GitHub Reviewed Published Dec 25, 2022 to the GitHub Advisory Database • Updated Mar 1, 2024

Package

gomod code.sajari.com/docconv (Go)

Affected versions

< 1.2.1

Patched versions

1.2.1
gomod github.com/sajari/docconv (Go)
< 1.2.1
1.2.1

Description

A vulnerability was found in docconv up to 1.2.0 and classified as problematic. This issue affects the function ConvertDocx/ConvertODT/ConvertPages/ConvertXML/XMLToText. The manipulation leads to uncontrolled memory allocation. The attack may be initiated remotely. Upgrading to version 1.2.1 can address this issue. The name of the patch is 42bcff666855ab978e67a9041d0cdea552f20301. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-216779.

References

Published by the National Vulnerability Database Dec 25, 2022
Published to the GitHub Advisory Database Dec 25, 2022
Reviewed Dec 30, 2022
Last updated Mar 1, 2024

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

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

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H

EPSS score

0.185%
(57th percentile)

Weaknesses

CVE ID

CVE-2022-4741

GHSA ID

GHSA-qvx2-59g8-8hph

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.