CVE-2018-19139
Description
A vulnerability was found in JasPer where a memory leak occurs in jas_malloc.c when called from jpc_unk_getparms in jpc_cs.c where, an attacker could exploit this flaw by persuading a victim to open a specially crafted file, causing excessive memory consumption and eventually crashing the application.
Déclaration
This vulnerability was rated as LOW severity because it requires a specially crafted file to exploit, leading to a memory leak. While it doesn't cause immediate security compromise, it can cause the application to crash due to excessive memory usage.
Détails du score du système commun d'évaluation des vulnérabilités (CVSS)
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
Les mesures et les scores CVSS suivants sont préliminaires et sujets à révision.
Répartition des scores CVSS v3
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Score de base | 3.3 | 5.5 | N/A |
| Vecteur d'attaque | Local | Local | N/A |
| Complexité de l'attaque | Low | Low | N/A |
| Privilèges requis | None | None | N/A |
| Interaction avec l'utilisateur | Required | Required | N/A |
| Champ d'application | Unchanged | Unchanged | N/A |
| Confidentialité | None | None | N/A |
| Impact sur l'intégrité | None | None | N/A |
| Impact sur la disponibilité | Low | High | N/A |
Vecteur
Red Hat: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:L
NVD: CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H
Comprendre la Défaillance (CWE)
Availability
Technical Impact: DoS: Crash, Exit, or Restart; DoS: Resource Consumption (CPU); DoS: Resource Consumption (Memory); DoS: Resource Consumption (Other)
If an attacker can trigger the allocation of the limited resources, but the number or size of the resources is not controlled, then the most common result is denial of service. This would prevent valid users from accessing the product, and it could potentially have an impact on the surrounding environment, i.e., the product may slow down, crash due to unhandled errors, or lock out legitimate users. For example, a memory exhaustion attack against an application could slow down the application as well as its host operating system.
Access Control,Other
Technical Impact: Bypass Protection Mechanism; Other
In some cases it may be possible to force the product to "fail open" in the event of resource exhaustion. The state of the product -- and possibly the security functionality - may then be compromised.
Questions fréquemment posées
Not sure what something means? Check out our Security Glossary.
Vous souhaitez recevoir des notifications d'errata ? Signez ici.