CVE-2023-37035
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 · uneditedA Null pointer dereference vulnerability in the Mobile Management Entity (MME) in Magma <= 1.8.0 (fixed in v1.9 commit 08472ba98b8321f802e95f5622fa90fec2dea486) allows network-adjacent attackers to crash the MME via an S1AP `S1Setup Request` packet missing an expected `Global eNB ID` field.
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 confidenceA null pointer dereference vulnerability exists in Magma's Mobile Management Entity (MME) where processing an S1AP S1Setup Request packet missing the Global eNB ID field causes the MME to crash. An attacker on the adjacent network can send a malformed S1Setup Request to trigger this denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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 if Magma MME is deployedSearch for running magma-mme service or container: 'docker ps | grep mme' or 'systemctl list-units | grep magma' or check kubernetes pods with label 'app=mme'Affected if Magma MME service is found running in the environment
-
Determine installed Magma versionRun 'magma агент version' or check the docker image tag: 'docker images | grep magma' or inspect the Helm chart version if deployed via KubernetesAffected if Version is below 1.9 (v1.8.x or earlier)
-
Verify S1AP interface exposure to adjacent networkReview network configuration: check if S1AP port (3642) is bound to an interface accessible from adjacent networks, or inspect firewall rules for inbound access to port 3642 from untrusted sourcesAffected if S1AP interface is reachable from adjacent (untrusted) networks without proper network filtering
-
Check for MME crash logs related to S1Setup RequestReview MME service logs for crash indicators: 'journalctl -u magma-mme -g crash' or 'kubectl logs <mme-pod> -grep S1Setup' or check /var/log/magma/mme.log for null pointer or segmentation fault entries mentioning S1SetupAffected if Recent crash logs indicate MME termination triggered by S1Setup Request processing
-
Inspect S1AP message handling configurationIf code is accessible, verify S1AP S1Setup handler validates Global eNB ID presence before dereferencing. Check source file s1ap_handler.c or equivalent for null check on global_enb_idAffected if Global eNB ID validation is missing in the S1Setup Request handler (code-level check)
-
Verify service availability on S1AP portTest connectivity to S1AP service: 'nc -zv <mme-ip> 3642' or 'telnet <mme-ip> 3642' to confirm MME is listening on the S1 interfaceAffected if MME S1AP service is active and reachable, making it potentially vulnerable to malformed requests
Environment is affected if Magma MME version is below 1.9 and the S1AP interface is exposed to adjacent (untrusted) networks, allowing an attacker to send malformed S1Setup Request packets missing the Global eNB ID field.
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 · scopedUpgrade Magma to version 1.9 or later (commit 08472ba98b8321f802e95f5622fa90fec2dea486) which includes the fix. Consider implementing input validation at network boundaries as an additional defense-in-depth measure.
v1.9
- 1. Back up current Magma configuration and database
- 2. Ensure the system meets prerequisites for Magma v1.9
- 3. Stop the Magma MME service
- 4. Upgrade Magma to version 1.9 using the standard upgrade process (e.g., via Ansible, Helm, or package manager depending on deployment)
- 5. Verify the MME service starts successfully
- 6. Test S1AP connectivity to confirm the MME handles S1Setup Request packets correctly
- 7. Monitor logs for any errors related to NULL pointer dereference
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37035 — 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-2023-37035 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