Security readout for executives and security teams
Plain-English summary
This Juniper SRX issue can make affected firewalls consume memory until they stop providing service. It only applies when SSL Proxy and UTM Web-Filtering are both in use. Recovery requires rebooting the device, so exposed internet-edge or branch firewalls could cause meaningful outage risk.
Executive priority
Treat as a high-priority availability risk for affected SRX firewalls. The scope is narrow, but the impact can be business-disrupting because service restoration requires rebooting the device.
Technical view
CVE-2023-36831 is CWE-703 improper handling of exceptional conditions in Junos OS UTM Web-Filtering on SRX Series. Certain website access under SSL Proxy plus UTM Web-Filtering causes a jbuf memory leak, eventually producing denial of service. Affected trains are 22.2, 22.3, and 22.4 before listed fixed releases.
Likely exposure
Exposure is limited to Juniper SRX Series running affected Junos OS versions with both SSL Proxy and UTM Web-Filtering configured. Other products, platforms, configurations, and Junos versions before 22.2R2 are stated as unaffected.
Exploitation context
The CVSS vector indicates network reachability, low complexity, no privileges, and no user interaction, with high availability impact. The provided data does not show CISA KEV listing or cited evidence of active exploitation.
Researcher notes
Evidence supports configuration-dependent DoS, not confidentiality or integrity impact. The bundle does not include exploit details, telemetry, or active exploitation confirmation. Validation should focus on version, SRX platform, and combined SSL Proxy plus UTM Web-Filtering exposure.
Mitigation direction
- Upgrade 22.2 deployments to 22.2R3 or later.
- Upgrade 22.3 deployments to 22.3R2-S1, 22.3R3, or later.
- Upgrade 22.4 deployments to 22.4R1-S2, 22.4R2, or later.
- Check Juniper advisory JSA71636 before applying operational workarounds.
- Prioritize maintenance windows for SRX devices handling critical ingress or branch traffic.
Validation and detection
- Inventory SRX devices and record Junos OS release trains.
- Confirm whether SSL Proxy and UTM Web-Filtering are both enabled.
- Compare installed versions against Juniper’s fixed release list.
- Review device health for jbuf memory growth and unexplained DoS symptoms.
- Verify upgraded devices are no longer on affected pre-fix releases.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-703: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2023-36831 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://supportportal.juniper.net/JSA71636CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Check or Handling of Exceptional Conditions
Improper Check or Handling of Exceptional Conditions represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.