dbcve.org
SecurityApplication · Kaspersky

CVE-2024-1619

HIGH · 8.8 CVSS v3.1 Published 2024-02-29
Fix available
A fix is available. Upgrade to after 8.0.3.30 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Kaspersky has fixed a security issue in the Kaspersky Security 8.0 for Linux Mail Server. The issue was that an attacker could potentially force an administrator to click on a malicious link to perform unauthorized actions.

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 confidence

This is a Cross-Site Request Forgery (CSRF) vulnerability in Kaspersky Security 8.0 for Linux Mail Server. An unauthenticated attacker could craft malicious links that, when clicked by an authenticated administrator, could trick the admin's browser into sending unintended requests to perform unauthorized administrative actions on the mail server.

MitigationApply the vendor patch from Kaspersky to obtain the fixed version. Additionally, implement anti-CSRF tokens in all state-changing operations within the web management interface to prevent forced request execution.

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
SecurityApplication
Affected:>= 8.0, <= 8.0.3.30

CVSS 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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Kaspersky Security for Linux Mail Server is installed
    Check for the presence of Kaspersky Security 8.0 for Linux Mail Server on the system. Look for installation directories or use package management tools to list installed Kaspersky products.
    Affected if The product is not installed on the system.
  2. Identify installed version
    Retrieve the installed version of Kaspersky Security for Linux Mail Server. Common methods include checking the application version via command line, reviewing installation logs, or querying the package manager for the installed Kaspersky Security version.
    Affected if The installed version is between 8.0 and 8.0.3.30 inclusive.
  3. Verify web management interface is enabled
    Determine if the web management interface for Kaspersky Security 8.0 for Linux Mail Server is enabled and accessible. Check the configuration settings or service status that controls web interface access.
    Affected if The web management interface is enabled and exposed to network access.
  4. Check for CSRF token protection
    Inspect the web management interface requests, particularly state-changing operations like configuration modifications or administrative actions, to determine if anti-CSRF tokens are implemented in the requests.
    Affected if Anti-CSRF tokens are NOT present in state-changing operations.

A system is affected if Kaspersky Security 8.0 for Linux Mail Server is installed with a version between 8.0 and 8.0.3.30 inclusive AND the web management interface is enabled, regardless of whether anti-CSRF tokens are present.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 8.0.3.30
Interim mitigation

Apply the vendor patch from Kaspersky to obtain the fixed version. Additionally, implement anti-CSRF tokens in all state-changing operations within the web management interface to prevent forced request execution.

Recommended fix Moderate confidence

Kaspersky Security 8.0 for Linux Mail Server version > 8.0.3.30 (check support.kaspersky.com for exact fixed release number)

  1. Check Kaspersky support portal (support.kaspersky.com) for the specific fixed version of Security 8.0 for Linux Mail Server
  2. Locate the patch or updated version for CVE-2024-1619
  3. Download and install the updated version from official Kaspersky channels
  4. After upgrade, verify the web interface is accessible and confirm the version number matches the fixed release
  5. Review administrator sessions and consider invalidating existing sessions as a precaution

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-1619 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-1619 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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