CVE-2024-46658
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 · uneditedSyrotech SY-GOPON-8OLT-L3 v1.6.0_240629 was discovered to contain an authenticated command injection vulnerability.
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 · moderate confidenceThe Syrotech SY-GOPON-8OLT-L3 v1.6.0_240629 contains an authenticated command injection vulnerability, allowing authenticated users to execute arbitrary system commands on the device through insufficient input sanitization in the web interface or CLI.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/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.
-
Confirm device model and firmware versionAccess the device console, web interface, or check the startup banner via CLI (telnet/ssh) to identify the exact firmware version. For web interface, check the 'System Info' or 'Device Status' page. For CLI, use 'show version' or 'system info' command.Affected if The device is a Syrotech SY-GOPON-8OLT-L3 running firmware version v1.6.0_240629 exactly, or any version within the v1.6.0_x release line prior to patching.
-
Verify web management interface is accessibleAttempt to access the device's web interface by navigating to its IP address on ports 80 or 443 using a web browser. Confirm the interface loads and presents a login page.Affected if The web interface is exposed and accessible from network segments where untrusted users could potentially obtain credentials.
-
Verify CLI access is enabledAttempt to connect to the device via telnet (port 23) or SSH (port 22) using the device's IP address. Confirm a login prompt appears.Affected if CLI (telnet or SSH) is enabled and accessible from network segments where untrusted users could potentially obtain credentials.
-
Check authentication configuration statusLog into the device via web interface or CLI and navigate to user management or administrator settings. Verify whether local user accounts exist, whether default credentials are still in use, and whether strong authentication is enforced.Affected if The device has active user accounts with administrative privileges accessible via web or CLI, especially if default credentials have not been changed.
Your environment is affected if you operate a Syrotech SY-GOPON-8OLT-L3 on firmware v1.6.0_240629 (or similar v1.6.0_x builds) and have the web interface or CLI accessible with active authentication, allowing authenticated users to submit input that could be vulnerable to command injection.
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.
From vendor dataApply vendor-supplied firmware patch when available; if no patch exists, restrict administrative access to trusted networks and implement network segmentation to limit exposure.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-46658 — 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-46658 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