CERTFR-2022-AVI-233

Vulnerability from certfr_avis - Published: - Updated:

Une vulnérabilité a été découverte dans les produits F-Secure. Elle permet à un attaquant de provoquer une exécution de code arbitraire.

Solution

Se référer au bulletin de sécurité de l'éditeur pour l'obtention des correctifs (cf. section Documentation).

  • F-Secure Client Security versions antérieures à 15.30
  • F-Secure Server Security versions antérieures à 15.30
  • F-Secure Email and Server Security versions 15.x sans le correctif de sécurité fscs1530-hf02-signed.jar
  • F-Secure Elements Agent
  • F-Secure MDR
  • F-Secure FREEDOME VPN
  • F-Secure SAFE
  • F-Secure KEY
  • F-Secure Internet Security / Anti-Virus

Le correctif de sécurité doit être installé manuellement sur tous les produits de la suite F-Secure Business (F-Secure Client Security, F-Secure Server Security et F-Secure Email and Server Security).

Ce correctif est installé au travers du canal de mises à jour automatiques pour tous les autres environnements.

Impacted products
Vendor Product Description
References

Show details on source website

{
  "$ref": "https://www.cert.ssi.gouv.fr/openapi.json",
  "affected_systems": [],
  "affected_systems_content": "\u003cul\u003e \u003cli\u003eF-Secure Client Security versions ant\u00e9rieures \u00e0 15.30\u003c/li\u003e \u003cli\u003eF-Secure Server Security versions ant\u00e9rieures \u00e0 15.30\u003c/li\u003e \u003cli\u003eF-Secure Email and Server Security versions 15.x sans le correctif de s\u00e9curit\u00e9 fscs1530-hf02-signed.jar\u003c/li\u003e \u003cli\u003eF-Secure Elements Agent\u003c/li\u003e \u003cli\u003eF-Secure MDR\u003c/li\u003e \u003cli\u003eF-Secure FREEDOME VPN\u003c/li\u003e \u003cli\u003eF-Secure SAFE\u003c/li\u003e \u003cli\u003eF-Secure KEY\u003c/li\u003e \u003cli\u003eF-Secure Internet Security / Anti-Virus\u003c/li\u003e \u003c/ul\u003e \u003cp\u003eLe correctif de s\u00e9curit\u00e9 doit \u00eatre install\u00e9 manuellement sur tous les produits de la suite F-Secure Business (F-Secure Client Security, F-Secure Server Security et F-Secure Email and Server Security).\u003c/p\u003e \u003cp\u003eCe correctif est install\u00e9 au travers du canal de mises \u00e0 jour automatiques pour tous les autres environnements.\u003c/p\u003e ",
  "content": "## Solution\n\nSe r\u00e9f\u00e9rer au bulletin de s\u00e9curit\u00e9 de l\u0027\u00e9diteur pour l\u0027obtention des\ncorrectifs (cf. section Documentation).\n",
  "cves": [
    {
      "name": "CVE-2021-44750",
      "url": "https://www.cve.org/CVERecord?id=CVE-2021-44750"
    }
  ],
  "links": [],
  "reference": "CERTFR-2022-AVI-233",
  "revisions": [
    {
      "description": "Version initiale",
      "revision_date": "2022-03-10T00:00:00.000000"
    }
  ],
  "risks": [
    {
      "description": "Ex\u00e9cution de code arbitraire"
    }
  ],
  "summary": "Une vuln\u00e9rabilit\u00e9 a \u00e9t\u00e9 d\u00e9couverte dans les produits F-Secure. Elle\npermet \u00e0 un attaquant de provoquer une ex\u00e9cution de code arbitraire.\n",
  "title": "Vuln\u00e9rabilit\u00e9 dans les produits F-Secure",
  "vendor_advisories": [
    {
      "published_at": null,
      "title": "Bulletin de s\u00e9curit\u00e9 F-Secure du 09 mars 2022",
      "url": "https://www.f-secure.com/en/business/support-and-downloads/security-advisories/cve-2021-44750"
    }
  ]
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Sightings

Author Source Type Date

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Loading…

Detection rules are retrieved from Rulezet.

Loading…

Loading…