Security readout for executives and security teams
Plain-English summary
An internet-reachable SPON IP Network Broadcast System may let an unauthenticated attacker read sensitive server files. Exposed configuration or credential files could enable broader compromise. The affected version range is undefined, so organizations cannot safely exclude installations by version alone.
Executive priority
Prioritize immediate exposure assessment for internet-facing systems and apply network restrictions promptly. The flaw can disclose credentials or configuration without authentication, while version-based triage is currently unreliable. Escalate confirmed exposure or suspicious access to incident-response teams.
Technical view
CVE-2024-13982 is a CWE-22 directory-traversal flaw in rj_get_token.php. Insufficient validation of jsondata[url] can permit remote, unauthenticated arbitrary file reads. CVSS 4.0 rates it 8.7, reflecting low-complexity network access and high confidentiality impact, without demonstrated integrity or availability impact.
Likely exposure
Highest risk applies where the vulnerable endpoint is reachable from the internet or untrusted networks. All discovered SPON IP Network Broadcast System installations should be treated as potentially affected because no reliable affected or fixed version range is provided.
Exploitation context
Public technical material is referenced, increasing the likelihood that attackers can understand the flaw. However, the source bundle reports no CISA KEV listing and provides no evidence of active exploitation. Exploitation status should therefore be treated as unconfirmed.
Researcher notes
The supplied record identifies parameter-level traversal but does not define affected versions, product CPEs, a fixed release, or vendor remediation. Validate defensively without accessing sensitive file contents. Separate evidence of endpoint exposure from evidence of successful exploitation.
Mitigation direction
- Identify and restrict access to rj_get_token.php from untrusted networks.
- Place management interfaces behind authenticated VPN or equivalent network controls.
- Monitor requests to the endpoint for traversal indicators and unusual file access patterns.
- Check SPON guidance for confirmed affected versions, patches, or supported mitigations.
- Rotate potentially exposed credentials if suspicious access or confirmed exposure is found.
Validation and detection
- Inventory SPON IP Network Broadcast System deployments and their network reachability.
- Confirm whether rj_get_token.php exists and is accessible without authentication.
- Review web, application, and security logs for suspicious requests to the endpoint.
- Determine whether sensitive files or credentials could be accessed by the service account.
- Record product versions, but do not infer safety because the affected range is undefined.
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-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. 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 lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2024-13982 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
- 8.7 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
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.
SSVC decision data
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:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
8.7HighVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://blog.csdn.net/qq_36618918/article/details/135505570CVE reference, VulnCheck · technical-description, exploit
- https://sponcomm.com/collections/ip-intercom-systemCVE reference, VulnCheck · product
- https://www.vulncheck.com/advisories/spon-ip-network-intercom-system-arbitrary-file-readCVE reference, VulnCheck · third-party-advisory
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 Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.