NN-2023:10-01
Vulnerability from csaf_nozominetworks - Published: 2023-09-18 11:00 - Updated: 2024-09-19 11:00| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Nozomi Networks Guardian 22.6.3
Nozomi Networks / Guardian
|
22.6.3 | ||
|
Nozomi Networks Guardian 23.1.0
Nozomi Networks / Guardian
|
23.1.0 | ||
|
Nozomi Networks CMC 22.6.3
Nozomi Networks / CMC
|
22.6.3 | ||
|
Nozomi Networks CMC 23.1.0
Nozomi Networks / CMC
|
23.1.0 |
| Product | Identifier | Version | Remediation |
|---|---|---|---|
|
Nozomi Networks Guardian >=22.6.0|<22.6.3
Nozomi Networks / Guardian
|
vers:gem/>=22.6.0|<22.6.3 |
Mitigation
Vendor Fix
|
|
|
Nozomi Networks Guardian >=23.0.0|<23.1.0
Nozomi Networks / Guardian
|
vers:gem/>=23.0.0|<23.1.0 |
Mitigation
Vendor Fix
|
|
|
Nozomi Networks CMC >=22.6.0|<22.6.3
Nozomi Networks / CMC
|
vers:gem/>=22.6.0|<22.6.3 |
Mitigation
Vendor Fix
|
|
|
Nozomi Networks CMC >=23.0.0|<23.1.0
Nozomi Networks / CMC
|
vers:gem/>=23.0.0|<23.1.0 |
Mitigation
Vendor Fix
|
{
"document": {
"aggregate_severity": {
"text": "HIGH"
},
"category": "csaf_vex",
"csaf_version": "2.0",
"distribution": {
"tlp": {
"label": "WHITE"
}
},
"lang": "en-US",
"notes": [
{
"category": "other",
"text": "High",
"title": "Risk Level for Nozomi customers"
}
],
"publisher": {
"category": "vendor",
"contact_details": "Nozomi Networks Product Security team can be reached at prodsec@nozominetworks.com",
"name": "Nozomi Networks Product Security",
"namespace": "https://security.nozominetworks.com/psirt"
},
"title": "DoS on IDS parsing of malformed asset fields in Guardian/CMC \u003e= 22.6.0 before 22.6.3 and 23.1.0",
"tracking": {
"aliases": [
"CVE-2023-32649"
],
"current_release_date": "2024-09-19T11:00:00.000Z",
"id": "NN-2023:10-01",
"initial_release_date": "2023-09-18T11:00:00.000Z",
"revision_history": [
{
"date": "2023-09-18T11:00:00.000Z",
"number": "1",
"summary": "Initial revision"
},
{
"date": "2023-11-13T11:00:00.000Z",
"number": "2",
"summary": "Migrated to CSAF VEX format"
},
{
"date": "2023-11-16T11:00:00.000Z",
"number": "3",
"summary": "CSAF vers improvements"
},
{
"date": "2024-05-20T11:00:00.000Z",
"number": "4",
"summary": "Added CVSS v4.0 scoring where applicable"
},
{
"date": "2024-09-19T11:00:00.000Z",
"number": "5",
"summary": "Revised CWE mapping"
}
],
"status": "final",
"version": "5"
}
},
"product_tree": {
"branches": [
{
"branches": [
{
"branches": [
{
"category": "product_version_range",
"name": "vers:gem/\u003e=22.6.0|\u003c22.6.3",
"product": {
"name": "Nozomi Networks Guardian \u003e=22.6.0|\u003c22.6.3",
"product_id": "CSAFPID-0001"
}
},
{
"category": "product_version_range",
"name": "vers:gem/\u003e=23.0.0|\u003c23.1.0",
"product": {
"name": "Nozomi Networks Guardian \u003e=23.0.0|\u003c23.1.0",
"product_id": "CSAFPID-0002"
}
},
{
"category": "product_version",
"name": "22.6.3",
"product": {
"name": "Nozomi Networks Guardian 22.6.3",
"product_id": "CSAFPID-0003"
}
},
{
"category": "product_version",
"name": "23.1.0",
"product": {
"name": "Nozomi Networks Guardian 23.1.0",
"product_id": "CSAFPID-0004"
}
}
],
"category": "product_name",
"name": "Guardian"
},
{
"branches": [
{
"category": "product_version_range",
"name": "vers:gem/\u003e=22.6.0|\u003c22.6.3",
"product": {
"name": "Nozomi Networks CMC \u003e=22.6.0|\u003c22.6.3",
"product_id": "CSAFPID-0005"
}
},
{
"category": "product_version_range",
"name": "vers:gem/\u003e=23.0.0|\u003c23.1.0",
"product": {
"name": "Nozomi Networks CMC \u003e=23.0.0|\u003c23.1.0",
"product_id": "CSAFPID-0006"
}
},
{
"category": "product_version",
"name": "22.6.3",
"product": {
"name": "Nozomi Networks CMC 22.6.3",
"product_id": "CSAFPID-0007"
}
},
{
"category": "product_version",
"name": "23.1.0",
"product": {
"name": "Nozomi Networks CMC 23.1.0",
"product_id": "CSAFPID-0008"
}
}
],
"category": "product_name",
"name": "CMC"
}
],
"category": "vendor",
"name": "Nozomi Networks"
}
]
},
"vulnerabilities": [
{
"acknowledgments": [
{
"organization": "Nozomi Networks",
"summary": "finding this issue during an internal investigation"
}
],
"cve": "CVE-2023-32649",
"cwe": {
"id": "CWE-1286",
"name": "Improper Validation of Syntactic Correctness of Input"
},
"discovery_date": "2023-09-18T11:00:00.000Z",
"ids": [
{
"system_name": "Nozomi Networks Security Advisory ID",
"text": "NN-2023:10-01"
}
],
"notes": [
{
"category": "summary",
"text": "A Denial of Service (Dos) vulnerability in Nozomi Networks Guardian and CMC, due to improper input validation in certain fields used in the Asset Intelligence functionality of our IDS, allows an unauthenticated attacker to crash the IDS module by sending specially crafted malformed network packets.",
"title": "Vulnerability summary"
}
],
"product_status": {
"fixed": [
"CSAFPID-0003",
"CSAFPID-0004",
"CSAFPID-0007",
"CSAFPID-0008"
],
"known_affected": [
"CSAFPID-0001",
"CSAFPID-0002",
"CSAFPID-0005",
"CSAFPID-0006"
]
},
"references": [
{
"category": "external",
"summary": "Mitre CVE entry",
"url": "https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2023-32649"
},
{
"category": "self",
"summary": "Canonical URL",
"url": "https://security.nozominetworks.com/csaf/2023/nn-2023_10-01.json"
},
{
"category": "self",
"summary": "Human-readable advisory.",
"url": "https://security.nozominetworks.com/NN-2023:10-01"
}
],
"remediations": [
{
"category": "mitigation",
"details": "N/A. It is recommended to monitor the IDS log to check for abnormal stops and restarts.",
"product_ids": [
"CSAFPID-0001",
"CSAFPID-0002",
"CSAFPID-0005",
"CSAFPID-0006"
]
},
{
"category": "vendor_fix",
"details": "Upgrade to v22.6.3, v23.1.0 or later.",
"product_ids": [
"CSAFPID-0001",
"CSAFPID-0002",
"CSAFPID-0005",
"CSAFPID-0006"
]
}
],
"scores": [
{
"cvss_v3": {
"baseScore": 7.5,
"baseSeverity": "HIGH",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H",
"version": "3.1"
},
"products": [
"CSAFPID-0001",
"CSAFPID-0002",
"CSAFPID-0005",
"CSAFPID-0006"
]
}
],
"threats": [
{
"category": "impact",
"details": "During the (limited) time window before the IDS module is automatically restarted, network traffic may not be analyzed."
}
],
"title": "DoS on IDS parsing of malformed asset fields in Guardian/CMC \u003e= 22.6.0 before 22.6.3 and 23.1.0"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
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.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.