cve.bz

CVE-2019-0214 apache archiva

6.5 mediumEPSS 4.8%Fix available

Medium (6.5) in apache archiva. EPSS 4.8% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.archiva:archiva 2.2.4.

On this page
In Apache Archiva 2.0.0 - 2.2.3, it is possible to write files to the archiva server at arbitrary locations by using the artifact upload mechanism. Existing files can be overwritten, if the archiva run user has appropriate permission on the filesystem for the target file.

Severity

CVSS 3.0

6.5 medium
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
EPSS
4.8% (unchanged from 4.8% a week ago; 4.8% 30 days ago) estimated probability of exploitation activity in the next 30 days; 92nd percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2019-0214 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2019-0214?via=ask-ai-copy and https://cve.bz/cve/CVE-2019-0214?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2019-0214 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
apache:archivafrom 1.2 through 1.3.9
apache:archivafrom 2.0.0 through 2.2.3

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-jxgm-9f58-w4xpMavenorg.apache.archiva:archiva>=2.2.0 <2.2.42.2.4

References

Check your stackJSON