CVE-2024-47498
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 · uneditedAn Unimplemented or Unsupported Feature in UI vulnerability in the CLI of Juniper Networks Junos OS Evolved on QFX5000 Series allows an unauthenticated, adjacent attacker to cause a Denial-of-Service (DoS). Several configuration statements meant to enforce limits on MAC learning and moves can be configured but do not take effect. This can lead to control plane overload situations which will severely impact the ability of the device to processes legitimate traffic. This issue affects Junos OS Evolved on QFX5000 Series: * All versions before 21.4R3-S8-EVO, * 22.2-EVO versions before 22.2R3-S5-EVO, * 22.4-EVO versions before 22.4R3-EVO, * 23.2-EVO versions before 23.2R2-EVO.
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 · high confidenceOn Juniper Junos OS Evolved for QFX5000 Series, certain configuration statements intended to enforce limits on MAC learning and MAC moves can be configured through the CLI but do not actually get enforced. This creates an unimplemented feature vulnerability where an unauthenticated adjacent attacker can trigger excessive MAC learning, leading to control plane overload and a denial-of-service condition.
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< 21.4= 21.4= 22.2= 22.4= 23.2CVSS 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
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device model and OS typeRun 'show system information' or 'show chassis hardware' to confirm the device is a QFX5000 series switch running Junos OS EvolvedAffected if Device is a QFX5000 series switch running Junos OS Evolved
-
Check the Junos OS Evolved versionRun 'show version' to obtain the installed software versionAffected if Version is < 21.4, 21.4, 22.2, 22.4, or 23.2
-
Identify MAC learning limit configurationRun 'show configuration protocols layer2-control mac-table-size' or 'show configuration protocols layer2-control mac-limit' to see if MAC table size limits are configuredAffected if MAC table size or MAC limit configuration statements exist in the active configuration
-
Identify MAC move limit configurationRun 'show configuration protocols layer2-control mac-move-limit' or search for 'mac-move' in the configuration to see if MAC move limits are configuredAffected if MAC move limit configuration statements exist in the active configuration
-
Verify MAC limit enforcementAttempt to add more MAC addresses than the configured limit to see if the limit is actually enforced, or monitor MAC learning behavior under high MAC traffic conditionsAffected if Configured MAC limits or MAC move limits are not being enforced (MAC addresses continue to be learned beyond configured limits)
If the device is a QFX5000 series on Junos OS Evolved with a version in the affected list AND has MAC table size or MAC move limit configurations that are not being enforced, the environment is vulnerable to this CVE.
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.
dbcve · scoped21.4
Upgrade Junos OS Evolved to a patched version (21.4R3-S8-EVO, 22.2R3-S5-EVO, 22.4R3-EVO, or 23.2R2-EVO or later) to remediate this vulnerability.
21.4R3-S8-EVO, 22.2R3-S5-EVO, 22.4R3-EVO, or 23.2R2-EVO (or later)
- Identify the current Junos OS Evolved version running on the QFX5000 Series device using 'show version' command
- Plan upgrade to one of the fixed releases: 21.4R3-S8-EVO, 22.2R3-S5-EVO, 22.4R3-EVO, or 23.2R2-EVO (or later)
- Review Juniper Networks upgrade documentation and release notes for the target version
- Backup the current device configuration using 'request system configuration rescue save' or equivalent
- Download the appropriate upgrade image from Juniper Networks support portal
- Transfer the software image to the device and verify integrity per Juniper documentation
- Execute the upgrade following Juniper's standard upgrade procedure for Junos OS Evolved
- After upgrade, verify the device is operational and test that MAC learning limit configurations are now enforced properly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,728.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-47498 — 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-2024-47498 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