LiveActive security incident?Get immediate response
CVE Record

CVE-2017-9333: OpenWebif 1.2.5 allows remote code execution via a URL to the CallOPKG function in the IpkgController class...

OpenWebif 1.2.5 allows remote code execution via a URL to the CallOPKG function in the IpkgController class in plugin/controllers/ipkg.py, when the URL refers to an attacker-controlled web site with a Trojan horse package. This has security implications in cases where untrusted users can trigger CallOPKG calls, and these users can enter an arbitrary URL in an input field, even though that input field was only intended for a package name. This threat model may be relevant in the latest versions of third-party products that bundle OpenWebif, i.e., set-top box products. The issue of Trojan horse packages does NOT have security implications in cases where the attacker has full OpenWebif access.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This flaw affects OpenWebif 1.2.5. A user who can reach the package-management function could supply a URL to a hostile package instead of a package name, causing code execution when OpenWebif processes it. Business risk is highest for set-top box products or deployments bundling OpenWebif and exposing it to untrusted users.

Executive priority

Treat as high priority where OpenWebif is exposed beyond trusted administrators. The business concern is remote code execution through package handling, but urgency is lower for isolated or admin-only deployments. Asset discovery is the main first step because bundled product exposure is not fully enumerated.

Technical view

In plugin/controllers/ipkg.py, IpkgController CallOPKG accepted a URL where a package name was expected. If that URL points to an attacker-controlled site with a Trojan package, processing can lead to remote code execution. The CVE says this matters when untrusted users can trigger CallOPKG and provide arbitrary URLs.

Likely exposure

Confirmed exposure is OpenWebif 1.2.5. The CVE also flags possible exposure in third-party set-top box products that bundle OpenWebif, but does not name those products. Risk depends on whether untrusted users can access CallOPKG and enter arbitrary URLs.

Exploitation context

The provided sources do not show CISA KEV listing or confirmed active exploitation. The described attack requires access to trigger CallOPKG and provide an attacker-controlled package URL. The CVE states Trojan packages are not a meaningful added issue when the attacker already has full OpenWebif access.

Researcher notes

The public record provides a narrow threat model and limited affected-product metadata. Focus validation on OpenWebif 1.2.5, CallOPKG reachability, authorization boundaries, and URL handling. Do not assume all bundled products are affected without vendor confirmation.

Mitigation direction

  • Identify OpenWebif 1.2.5 deployments and bundled set-top box firmware.
  • Restrict OpenWebif access to trusted administrators and management networks.
  • Prevent untrusted users from invoking CallOPKG or package-management functions.
  • Check OpenWebif and device-vendor guidance for fixed versions or supported mitigations.
  • Review whether arbitrary URL input is accepted where package names are expected.

Validation and detection

  • Inventory OpenWebif versions across directly managed and bundled products.
  • Confirm whether CallOPKG is reachable by non-administrative or untrusted users.
  • Review package-management UI/API fields for arbitrary URL acceptance.
  • Check access logs for unexpected package-management requests.
  • Verify vendor advisories before declaring remediation complete.
Prepared
Confidence
medium
Sources
4

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

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.

description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2017-9333 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

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.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.