CVE-2019-15493
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedopenITCOCKPIT before 3.7.1 allows deletion of files, aka RVID 4-445b21.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceopenITCOCKPIT versions prior to 3.7.1 contain an arbitrary file deletion vulnerability that allows unauthenticated or low-privilege attackers to remove files from the system. The RVID 4-445b21 reference indicates this is a documented security flaw that could impact system integrity and availability by enabling malicious file removal.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 3.7.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if openITCOCKPIT is installedCheck for the presence of openITCOCKPIT by reviewing installed packages, web application directories, or the running services on the system. On Linux systems, you may use package managers like dpkg or rpm to list installed packages containing 'openitcockpit' or check common installation paths under /opt or /usr/share.Affected if openITCOCKPIT software is found on the system
-
Determine the installed openITCOCKPIT versionLocate the version information for openITCOCKPIT. This may be accessible via the web interface administration panel, a command-line tool provided by the application, or a version file within the application directory structure. Compare your discovered version against the affected version range.Affected if The installed version is lower than 3.7.1
-
Check for unauthenticated access to file deletion functionalityReview the openITCOCKPIT web application configuration and exposed endpoints to determine if the file deletion interface is accessible without authentication. This may involve examining the application's routing configuration, middleware settings, or access control lists.Affected if The file deletion functionality is accessible to unauthenticated or low-privilege users
-
Verify file system permission controlsInspect the file system permissions on critical directories and files used by openITCOCKPIT. Determine whether the web server process user has write access to sensitive system files beyond the application's intended scope.Affected if The web application process has excessive file system write permissions that could allow arbitrary file deletion outside intended directories
-
Review network exposure of management interfaceDetermine if the openITCOCKPIT management interface is accessible from untrusted networks by checking firewall rules, reverse proxy configuration, or network ACLs surrounding the host.Affected if The management interface is exposed to untrusted networks without proper access restrictions
A system is affected if openITCOCKPIT version 3.7.1 or later is not installed and the management interface or file deletion functionality is accessible to unauthorized users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data3.7.1
Upgrade openITCOCKPIT to version 3.7.1 or later. If immediate patching is not possible, restrict network access to the management interface and review file system permissions to limit the impact of unauthorized file deletion attempts.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15493 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-15493 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data