nday
CVE-2014-8730

F5 BIG-IP : cryptographic failure dans SSL profilesTitre composé par nday ; la fiche CVE n’en comporte pas.

Divulgation : . nday n’a encore aucune trace de correctif ; cela ne veut pas dire qu’il n’en existe pas. Cette vulnérabilité ne figure dans aucune des quatre sources de PoC. Aucune inscription au catalogue KEV de la CISA à ce jour.

why these tags

nday derives these tags by fixed rules from the facts below; NVD, the CNA and other sources do not assign them. Vocabulary and rules: ~/tags.

cryptographic failure
CWE-310, stated by NVD's analysts
network
AV:N in AV:N/AC:M/Au:N/C:P/I:N/A:N (CVSS 2.0) from NVD's analysts
no authentication required
Au:N in AV:N/AC:M/Au:N/C:P/I:N/A:N (CVSS 2.0) from NVD's analysts
F5 BIG-IP
CPE names NVD's analysts give as vulnerable: a:f5:big-ip_access_policy_manager, a:f5:big-ip_advanced_firewall_manager, a:f5:big-ip_analytics, a:f5:big-ip_application_acceleration_manager, a:f5:big-ip_application_security_manager, a:f5:big-ip_edge_gateway, a:f5:big-ip_local_traffic_manager, a:f5:big-ip_policy_enforcement_manager, a:f5:big-ip_protocol_security_module, a:f5:big-ip_wan_optimization_manager and 1 more
router / switch
CPE names NVD's analysts give as vulnerable: a:f5:big-ip_access_policy_manager, a:f5:big-ip_advanced_firewall_manager, a:f5:big-ip_analytics, a:f5:big-ip_application_acceleration_manager, a:f5:big-ip_application_security_manager, a:f5:big-ip_edge_gateway, a:f5:big-ip_local_traffic_manager, a:f5:big-ip_policy_enforcement_manager, a:f5:big-ip_protocol_security_module, a:f5:big-ip_wan_optimization_manager and 1 morethe product type of F5 BIG-IP in nday's product registry

CVSS 2.0 has no user-interaction metric, so “no user interaction” and “remote, unauthenticated” are never assigned from a CVSS 2.0 vector.

étape actuelle
DIS
divulgation
CVSS
pas encore de score

Cycle de vie

Axe en UTC ; point = minute exacte, barre large = date seule, creux = inconnue ou déduite.
date inconnue
DISdivulguée
2014-12-10T00:00Z
PATcorrectif
aucune donnée
ANAanalyse
aucune donnée
POCPoC
aucune donnée
ITWexploitée
aucune donnée
KEVKEV
aucune donnée

Résumé

The SSL profiles component in F5 BIG-IP LTM, APM, and ASM 10.0.0 through 10.2.4 and 11.0.0 through 11.5.1, AAM 11.4.0 through 11.5.1, AFM 11.3.0 through 11.5.1, Analytics 11.0.0 through 11.5.1, Edge Gateway, WebAccelerator, and WOM 10.1.0 through 10.2.4 and 11.0.0 through 11.3.0, PEM 11.3.0 through 11.6.0, and PSM 10.0.0 through 10.2.4 and 11.0.0 through 11.4.1 and BIG-IQ Cloud and Security 4.0.0 through 4.4.0 and Device 4.2.0 through 4.4.0, when using TLS 1.x before TLS 1.2, does not properly check CBC padding bytes when terminating connections, which makes it easier for man-in-the-middle attackers to obtain cleartext data via a padding-oracle attack, a variant of CVE-2014-3566 (aka POODLE). NOTE: the scope of this identifier is limited to the F5 implementation only. Other vulnerable implementations should receive their own CVE ID, since this is not a vulnerability within the design of TLS 1.x itself.

Original text of the CVE record (cvelist), shown as published.

Journal des événements

+DISdivulgation

Fiche CVE publiée par mitre.

source cvelist · importé en masse par nday le · brut
{
  "id": 142540,
  "type": "disclosed",
  "source": "cvelist",
  "url": "https://www.cve.org/CVERecord?id=CVE-2014-8730",
  "occurred_at": "2014-12-10T00:00:00Z",
  "observed_at": "2026-11-13T05:36:17.896178Z",
  "is_backfill": true,
  "dedupe_key": "",
  "detail": {
    "state": "PUBLISHED",
    "date_published": "2014-12-10T00:00:00.000Z",
    "assigner_short_name": "mitre"
  }
}

Report an error

report an error or omission

Something on this page wrong or missing? Tell the editors; if they accept it, this page's revision log says so publicly. Upstream data is not changed.

Échanges entre chercheurs

0 chercheur en a parlé ces 7 derniers jours

Publications sur X de chercheurs suivis par nday citant cette CVE, telles que publiées. nday ne les vérifie pas.

nday n’a encore recueilli aucune publication sur X d’un chercheur de sa liste citant cette CVE.

Discussion

0 comments

No comments yet.