Vulnerability-Lookup

CVE-2024-7346 (GCVE-0-2024-7346)

Vulnerability from cvelistv5 – Published: 2024-09-03 14:51 – Updated: 2024-09-03 15:06

Title

Client connections using default TLS certificates from OpenEdge may bypass TLS host name validation

Summary

Host name validation for TLS certificates is bypassed when the installed OpenEdge default certificates are used to perform the TLS handshake for a networked connection. This has been corrected so that default certificates are no longer capable of overriding host name validation and will need to be replaced where full TLS certificate validation is needed for network security. The existing certificates should be replaced with CA-signed certificates from a recognized certificate authority that contain the necessary information to support host name validation.

Severity ?

7.2 (High)


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

CWE

CWE-297 - Improper Validation of Certificate with Host Mismatch

Assigner

ProgressSoftware

References

URL

Tags

https://community.progress.com/s/article/Client-c…

vendor-advisory

Impacted products

	Vendor	Product	Version
	Progress	OpenEdge	Affected: 11.7.0 , ≤ 11.7.19 (custom) Affected: 12.2.0 , ≤ 12.2.14 (custom) Unaffected: 12.8.0 (custom)

Show details on NVD website

JSON

To clipboard

{
  "containers": {
    "adp": [
      {
        "affected": [
          {
            "cpes": [
              "cpe:2.3:a:progress:openedge:*:*:*:*:*:*:*:*"
            ],
            "defaultStatus": "affected",
            "product": "openedge",
            "vendor": "progress",
            "versions": [
              {
                "lessThanOrEqual": "11.7.19",
                "status": "affected",
                "version": "11.7.0",
                "versionType": "custom"
              },
              {
                "lessThanOrEqual": "12.2.14",
                "status": "affected",
                "version": "12.2.0",
                "versionType": "custom"
              },
              {
                "status": "unaffected",
                "version": "12.8.0"
              }
            ]
          }
        ],
        "metrics": [
          {
            "other": {
              "content": {
                "id": "CVE-2024-7346",
                "options": [
                  {
                    "Exploitation": "none"
                  },
                  {
                    "Automatable": "yes"
                  },
                  {
                    "Technical Impact": "partial"
                  }
                ],
                "role": "CISA Coordinator",
                "timestamp": "2024-09-03T15:03:24.623163Z",
                "version": "2.0.3"
              },
              "type": "ssvc"
            }
          }
        ],
        "providerMetadata": {
          "dateUpdated": "2024-09-03T15:06:04.578Z",
          "orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
          "shortName": "CISA-ADP"
        },
        "title": "CISA ADP Vulnrichment"
      }
    ],
    "cna": {
      "affected": [
        {
          "defaultStatus": "affected",
          "modules": [
            "PASOE Application Server",
            "OpenEdge Authentication Gateway"
          ],
          "platforms": [
            "Windows",
            "Linux",
            "64 bit",
            "x86",
            "32 bit"
          ],
          "product": "OpenEdge",
          "vendor": "Progress",
          "versions": [
            {
              "lessThanOrEqual": "11.7.19",
              "status": "affected",
              "version": "11.7.0",
              "versionType": "custom"
            },
            {
              "lessThanOrEqual": "12.2.14",
              "status": "affected",
              "version": "12.2.0",
              "versionType": "custom"
            },
            {
              "status": "unaffected",
              "version": "12.8.0",
              "versionType": "custom"
            }
          ]
        }
      ],
      "configurations": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Use of the legacy OpenEdge default TLS/SSL certificates in TLS-networked connections in an OpenEdge installation.\u003cbr\u003e"
            }
          ],
          "value": "Use of the legacy OpenEdge default TLS/SSL certificates in TLS-networked connections in an OpenEdge installation."
        }
      ],
      "descriptions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Host name validation for TLS certificates is bypassed when the installed OpenEdge default certificates are used to perform the TLS handshake for a networked connection.\u0026nbsp; This has been corrected so that default certificates are no longer capable of overriding host name validation and will need to be replaced where full TLS certificate validation is needed for network security.\u0026nbsp; The existing certificates should be replaced with CA-signed certificates from a recognized certificate authority that contain the necessary information to support host name validation.\u0026nbsp; \u003cbr\u003e\u003cbr\u003e"
            }
          ],
          "value": "Host name validation for TLS certificates is bypassed when the installed OpenEdge default certificates are used to perform the TLS handshake for a networked connection.\u00a0 This has been corrected so that default certificates are no longer capable of overriding host name validation and will need to be replaced where full TLS certificate validation is needed for network security.\u00a0 The existing certificates should be replaced with CA-signed certificates from a recognized certificate authority that contain the necessary information to support host name validation."
        }
      ],
      "impacts": [
        {
          "capecId": "CAPEC-272",
          "descriptions": [
            {
              "lang": "en",
              "value": "CAPEC-272: Protocol Manipulation"
            }
          ]
        }
      ],
      "metrics": [
        {
          "cvssV3_1": {
            "attackComplexity": "LOW",
            "attackVector": "NETWORK",
            "availabilityImpact": "NONE",
            "baseScore": 7.2,
            "baseSeverity": "HIGH",
            "confidentialityImpact": "LOW",
            "integrityImpact": "LOW",
            "privilegesRequired": "NONE",
            "scope": "CHANGED",
            "userInteraction": "NONE",
            "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
            "version": "3.1"
          },
          "format": "CVSS",
          "scenarios": [
            {
              "lang": "en",
              "value": "GENERAL"
            }
          ]
        }
      ],
      "problemTypes": [
        {
          "descriptions": [
            {
              "cweId": "CWE-297",
              "description": "CWE-297: Improper Validation of Certificate with Host Mismatch",
              "lang": "en",
              "type": "CWE"
            }
          ]
        }
      ],
      "providerMetadata": {
        "dateUpdated": "2024-09-03T14:51:03.551Z",
        "orgId": "f9fea0b6-671e-4eea-8fde-31911902ae05",
        "shortName": "ProgressSoftware"
      },
      "references": [
        {
          "tags": [
            "vendor-advisory"
          ],
          "url": "https://community.progress.com/s/article/Client-connections-using-default-TLS-certificates-from-OpenEdge-may-bypass-TLS-host-name-validation"
        }
      ],
      "solutions": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Use the 12.8.0 or above LTS release where the vulnerability does not exist\u003cbr\u003e"
            }
          ],
          "value": "Use the 12.8.0 or above LTS release where the vulnerability does not exist"
        },
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Use the 12.2 LTS release at the 12.2.15 Update level or above\n\n\u003cbr\u003e"
            }
          ],
          "value": "Use the 12.2 LTS release at the 12.2.15 Update level or above"
        },
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Use the 11.7 LTS release at the 11.7.20 Update level or above\n\n\u003cbr\u003e"
            }
          ],
          "value": "Use the 11.7 LTS release at the 11.7.20 Update level or above"
        }
      ],
      "source": {
        "discovery": "UNKNOWN"
      },
      "title": "Client connections using default TLS certificates from OpenEdge may bypass TLS host name validation",
      "workarounds": [
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "\u003cdiv\u003eReplace all use of default OpenEdge TLS certificates with a CA-signed certificate from a recognized certificate authority that contains the necessary information to support host name validation\n\n\u003cbr\u003e\u003c/div\u003e"
            }
          ],
          "value": "Replace all use of default OpenEdge TLS certificates with a CA-signed certificate from a recognized certificate authority that contains the necessary information to support host name validation"
        },
        {
          "lang": "en",
          "supportingMedia": [
            {
              "base64": false,
              "type": "text/html",
              "value": "Use the \"nohostverify\" switch in development environments when clients need to bypass host name validation as a convenience prior to establishing valid certificates for production.\u003cbr\u003e"
            }
          ],
          "value": "Use the \"nohostverify\" switch in development environments when clients need to bypass host name validation as a convenience prior to establishing valid certificates for production."
        }
      ],
      "x_generator": {
        "engine": "Vulnogram 0.2.0"
      }
    }
  },
  "cveMetadata": {
    "assignerOrgId": "f9fea0b6-671e-4eea-8fde-31911902ae05",
    "assignerShortName": "ProgressSoftware",
    "cveId": "CVE-2024-7346",
    "datePublished": "2024-09-03T14:51:03.551Z",
    "dateReserved": "2024-07-31T17:32:10.370Z",
    "dateUpdated": "2024-09-03T15:06:04.578Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.1",
  "vulnerability-lookup:meta": {
    "vulnrichment": {
      "containers": "{\"adp\": [{\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2024-7346\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"none\"}, {\"Automatable\": \"yes\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2024-09-03T15:03:24.623163Z\"}}}], \"affected\": [{\"cpes\": [\"cpe:2.3:a:progress:openedge:*:*:*:*:*:*:*:*\"], \"vendor\": \"progress\", \"product\": \"openedge\", \"versions\": [{\"status\": \"affected\", \"version\": \"11.7.0\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"11.7.19\"}, {\"status\": \"affected\", \"version\": \"12.2.0\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"12.2.14\"}, {\"status\": \"unaffected\", \"version\": \"12.8.0\"}], \"defaultStatus\": \"affected\"}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2024-09-03T15:05:02.299Z\"}}], \"cna\": {\"title\": \"Client connections using default TLS certificates from OpenEdge may bypass TLS host name validation\", \"source\": {\"discovery\": \"UNKNOWN\"}, \"impacts\": [{\"capecId\": \"CAPEC-272\", \"descriptions\": [{\"lang\": \"en\", \"value\": \"CAPEC-272: Protocol Manipulation\"}]}], \"metrics\": [{\"format\": \"CVSS\", \"cvssV3_1\": {\"scope\": \"CHANGED\", \"version\": \"3.1\", \"baseScore\": 7.2, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"HIGH\", \"vectorString\": \"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N\", \"integrityImpact\": \"LOW\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"LOW\", \"availabilityImpact\": \"NONE\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"LOW\"}, \"scenarios\": [{\"lang\": \"en\", \"value\": \"GENERAL\"}]}], \"affected\": [{\"vendor\": \"Progress\", \"modules\": [\"PASOE Application Server\", \"OpenEdge Authentication Gateway\"], \"product\": \"OpenEdge\", \"versions\": [{\"status\": \"affected\", \"version\": \"11.7.0\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"11.7.19\"}, {\"status\": \"affected\", \"version\": \"12.2.0\", \"versionType\": \"custom\", \"lessThanOrEqual\": \"12.2.14\"}, {\"status\": \"unaffected\", \"version\": \"12.8.0\", \"versionType\": \"custom\"}], \"platforms\": [\"Windows\", \"Linux\", \"64 bit\", \"x86\", \"32 bit\"], \"defaultStatus\": \"affected\"}], \"solutions\": [{\"lang\": \"en\", \"value\": \"Use the 12.8.0 or above LTS release where the vulnerability does not exist\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Use the 12.8.0 or above LTS release where the vulnerability does not exist\u003cbr\u003e\", \"base64\": false}]}, {\"lang\": \"en\", \"value\": \"Use the 12.2 LTS release at the 12.2.15 Update level or above\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Use the 12.2 LTS release at the 12.2.15 Update level or above\\n\\n\u003cbr\u003e\", \"base64\": false}]}, {\"lang\": \"en\", \"value\": \"Use the 11.7 LTS release at the 11.7.20 Update level or above\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Use the 11.7 LTS release at the 11.7.20 Update level or above\\n\\n\u003cbr\u003e\", \"base64\": false}]}], \"references\": [{\"url\": \"https://community.progress.com/s/article/Client-connections-using-default-TLS-certificates-from-OpenEdge-may-bypass-TLS-host-name-validation\", \"tags\": [\"vendor-advisory\"]}], \"workarounds\": [{\"lang\": \"en\", \"value\": \"Replace all use of default OpenEdge TLS certificates with a CA-signed certificate from a recognized certificate authority that contains the necessary information to support host name validation\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"\u003cdiv\u003eReplace all use of default OpenEdge TLS certificates with a CA-signed certificate from a recognized certificate authority that contains the necessary information to support host name validation\\n\\n\u003cbr\u003e\u003c/div\u003e\", \"base64\": false}]}, {\"lang\": \"en\", \"value\": \"Use the \\\"nohostverify\\\" switch in development environments when clients need to bypass host name validation as a convenience prior to establishing valid certificates for production.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Use the \\\"nohostverify\\\" switch in development environments when clients need to bypass host name validation as a convenience prior to establishing valid certificates for production.\u003cbr\u003e\", \"base64\": false}]}], \"x_generator\": {\"engine\": \"Vulnogram 0.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"Host name validation for TLS certificates is bypassed when the installed OpenEdge default certificates are used to perform the TLS handshake for a networked connection.\\u00a0 This has been corrected so that default certificates are no longer capable of overriding host name validation and will need to be replaced where full TLS certificate validation is needed for network security.\\u00a0 The existing certificates should be replaced with CA-signed certificates from a recognized certificate authority that contain the necessary information to support host name validation.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Host name validation for TLS certificates is bypassed when the installed OpenEdge default certificates are used to perform the TLS handshake for a networked connection.\u0026nbsp; This has been corrected so that default certificates are no longer capable of overriding host name validation and will need to be replaced where full TLS certificate validation is needed for network security.\u0026nbsp; The existing certificates should be replaced with CA-signed certificates from a recognized certificate authority that contain the necessary information to support host name validation.\u0026nbsp; \u003cbr\u003e\u003cbr\u003e\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-297\", \"description\": \"CWE-297: Improper Validation of Certificate with Host Mismatch\"}]}], \"configurations\": [{\"lang\": \"en\", \"value\": \"Use of the legacy OpenEdge default TLS/SSL certificates in TLS-networked connections in an OpenEdge installation.\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"Use of the legacy OpenEdge default TLS/SSL certificates in TLS-networked connections in an OpenEdge installation.\u003cbr\u003e\", \"base64\": false}]}], \"providerMetadata\": {\"orgId\": \"f9fea0b6-671e-4eea-8fde-31911902ae05\", \"shortName\": \"ProgressSoftware\", \"dateUpdated\": \"2024-09-03T14:51:03.551Z\"}}}",
      "cveMetadata": "{\"cveId\": \"CVE-2024-7346\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2024-09-03T15:06:04.578Z\", \"dateReserved\": \"2024-07-31T17:32:10.370Z\", \"assignerOrgId\": \"f9fea0b6-671e-4eea-8fde-31911902ae05\", \"datePublished\": \"2024-09-03T14:51:03.551Z\", \"assignerShortName\": \"ProgressSoftware\"}",
      "dataType": "CVE_RECORD",
      "dataVersion": "5.1"
    }
  }
}

GHSA-JW9P-3GC4-84RW

Vulnerability from github – Published: 2024-09-03 15:30 – Updated: 2024-09-05 15:33

Details

Severity ?

7.2 (High)


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

Show details on source website

JSON

To clipboard

{
  "affected": [],
  "aliases": [
    "CVE-2024-7346"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-287",
      "CWE-297"
    ],
    "github_reviewed": false,
    "github_reviewed_at": null,
    "nvd_published_at": "2024-09-03T15:15:16Z",
    "severity": "HIGH"
  },
  "details": "Host name validation for TLS certificates is bypassed when the installed OpenEdge default certificates are used to perform the TLS handshake for a networked connection.\u00a0 This has been corrected so that default certificates are no longer capable of overriding host name validation and will need to be replaced where full TLS certificate validation is needed for network security.\u00a0 The existing certificates should be replaced with CA-signed certificates from a recognized certificate authority that contain the necessary information to support host name validation.",
  "id": "GHSA-jw9p-3gc4-84rw",
  "modified": "2024-09-05T15:33:34Z",
  "published": "2024-09-03T15:30:46Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-7346"
    },
    {
      "type": "WEB",
      "url": "https://community.progress.com/s/article/Client-connections-using-default-TLS-certificates-from-OpenEdge-may-bypass-TLS-host-name-validation"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
      "type": "CVSS_V3"
    }
  ]
}

FKIE_CVE-2024-7346

Vulnerability from fkie_nvd - Published: 2024-09-03 15:15 - Updated: 2024-09-05 14:03

Severity ?

7.2 (High) - CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
4.8 (Medium) - CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N

Summary

References

	URL	Tags
	security@progress.com	https://community.progress.com/s/article/Client-connections-using-default-TLS-certificates-from-OpenEdge-may-bypass-TLS-host-name-validation	Mitigation, Vendor Advisory

Impacted products

	Vendor	Product	Version
	progress	openedge	*
	progress	openedge	*

JSON

To clipboard

{
  "configurations": [
    {
      "nodes": [
        {
          "cpeMatch": [
            {
              "criteria": "cpe:2.3:a:progress:openedge:*:*:*:*:*:*:*:*",
              "matchCriteriaId": "148C3BEA-FD57-492F-9214-38FF9C128B67",
              "versionEndIncluding": "11.7.19",
              "vulnerable": true
            },
            {
              "criteria": "cpe:2.3:a:progress:openedge:*:*:*:*:lts:*:*:*",
              "matchCriteriaId": "D0C4BCF0-1423-4CC6-92E6-06485E069865",
              "versionEndIncluding": "12.2.14",
              "versionStartIncluding": "12.0",
              "vulnerable": true
            }
          ],
          "negate": false,
          "operator": "OR"
        }
      ]
    }
  ],
  "cveTags": [],
  "descriptions": [
    {
      "lang": "en",
      "value": "Host name validation for TLS certificates is bypassed when the installed OpenEdge default certificates are used to perform the TLS handshake for a networked connection.\u00a0 This has been corrected so that default certificates are no longer capable of overriding host name validation and will need to be replaced where full TLS certificate validation is needed for network security.\u00a0 The existing certificates should be replaced with CA-signed certificates from a recognized certificate authority that contain the necessary information to support host name validation."
    },
    {
      "lang": "es",
      "value": "La validaci\u00f3n del nombre de host para los certificados TLS se omite cuando se utilizan los certificados predeterminados de OpenEdge instalados para realizar el protocolo de enlace TLS para una conexi\u00f3n en red. Esto se ha corregido para que los certificados predeterminados ya no puedan anular la validaci\u00f3n del nombre de host y deban reemplazarse cuando se necesite una validaci\u00f3n completa del certificado TLS para la seguridad de la red. Los certificados existentes deben reemplazarse con certificados firmados por una autoridad de certificaci\u00f3n reconocida que contengan la informaci\u00f3n necesaria para admitir la validaci\u00f3n del nombre de host."
    }
  ],
  "id": "CVE-2024-7346",
  "lastModified": "2024-09-05T14:03:24.040",
  "metrics": {
    "cvssMetricV31": [
      {
        "cvssData": {
          "attackComplexity": "LOW",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 7.2,
          "baseSeverity": "HIGH",
          "confidentialityImpact": "LOW",
          "integrityImpact": "LOW",
          "privilegesRequired": "NONE",
          "scope": "CHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 3.9,
        "impactScore": 2.7,
        "source": "security@progress.com",
        "type": "Secondary"
      },
      {
        "cvssData": {
          "attackComplexity": "HIGH",
          "attackVector": "NETWORK",
          "availabilityImpact": "NONE",
          "baseScore": 4.8,
          "baseSeverity": "MEDIUM",
          "confidentialityImpact": "LOW",
          "integrityImpact": "LOW",
          "privilegesRequired": "NONE",
          "scope": "UNCHANGED",
          "userInteraction": "NONE",
          "vectorString": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N",
          "version": "3.1"
        },
        "exploitabilityScore": 2.2,
        "impactScore": 2.5,
        "source": "nvd@nist.gov",
        "type": "Primary"
      }
    ]
  },
  "published": "2024-09-03T15:15:16.913",
  "references": [
    {
      "source": "security@progress.com",
      "tags": [
        "Mitigation",
        "Vendor Advisory"
      ],
      "url": "https://community.progress.com/s/article/Client-connections-using-default-TLS-certificates-from-OpenEdge-may-bypass-TLS-host-name-validation"
    }
  ],
  "sourceIdentifier": "security@progress.com",
  "vulnStatus": "Analyzed",
  "weaknesses": [
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-297"
        }
      ],
      "source": "security@progress.com",
      "type": "Secondary"
    },
    {
      "description": [
        {
          "lang": "en",
          "value": "CWE-287"
        }
      ],
      "source": "nvd@nist.gov",
      "type": "Primary"
    }
  ]
}

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.

Detection rules are retrieved from Rulezet.

Action not permitted

CVE-2024-7346 (GCVE-0-2024-7346)

GHSA-JW9P-3GC4-84RW

FKIE_CVE-2024-7346

Tags

Sightings

Nomenclature