Port 22136FLIR Camera Protocol
The FLIR Systems Camera Resource Protocol is utilized primarily by FLIR network-enabled cameras to facilitate command, control, and data exchange. It enables remote configuration, firmware updates, and live video streaming capabilities, making it essential for surveillance, security applications, and industrial monitoring. Despite being a proprietary and unofficial protocol specification, it has gained traction across various FLIR hardware implementations..
- transport
- tcp
- in transit
- cleartext
- assignment
- unofficial
- risk
- 4/10
- lookups
- 9,127
single transport
payload readable on path
used by convention
caution
rank 536 of 993 · top 54%
Technical Details
what runs on :22136The FLIR Systems Camera Resource Protocol operates over TCP port 22136, facilitating communication between client applications and FLIR thermal imaging or visible spectrum cameras. It handles a wide range of functions such as camera initialization, parameter adjustment (like focus, zoom, and palette), firmware upgrades, and retrieval of camera status information.
Typically, the protocol transmits command-and-control packets encoded in FLIR’s proprietary formats, with sessions often initiated by dedicated client software or integrations in larger security management platforms. Some implementations allow for live video feed access or snapshot retrieval over the same port, streamlining operations for remote monitoring and diagnostics.
Due to its proprietary nature and lack of comprehensive public documentation, reverse engineering efforts have partially uncovered protocol behaviors. Integration often relies on SDKs or firmware-provided clients, and the protocol is heavily tailored towards embedded systems and surveillance infrastructures.
Security Information
exposure of :22136risk score
4/ 10caution
worth attention. how exposed you are depends on configuration — don't leave it reachable from the internet without a reason.
security averages 3.8 across 216 ports — this one sits 0.2 above.
in transit
cleartext
credentials and payloads are readable by anyone on path
assignment
unofficial
used by convention, not registered — what answers here varies by deployment
reachable over
tcp
every listening transport is another surface to filter at the edge
security overview
Common vulnerabilities related to FLIR Systems Camera Resource Protocol stem from:
- Unencrypted transmission allowing for eavesdropping, potentially exposing sensitive video streams or configuration data.
- Lack of strong authentication, making it vulnerable to unauthorized access and manipulation.
- Exposure of the service on public networks raising the risk of brute-force attacks or exploitation of firmware bugs.
Mitigation strategies include:
- Enforcing network segmentation to isolate camera management interfaces from untrusted networks.
- Deploying firewall rules to restrict access to authorized hosts.
- Applying firmware updates regularly to address security flaws.
- Implementing strong authentication mechanisms where supported, and disabling unused services or ports.
- Leveraging VPNs or private IP spaces when remote accessibility is necessary to add another security layer.
Related Ports
the 8 most looked-up other ports in security — 216 ports carry that label.
| port | service | risk | |||
|---|---|---|---|---|---|
| :8881 | Atlasz Secure Server | TCP | Web Services | caution | 67.6k |
| :443 | HTTPS | TCPtls | Web Services | caution | 65.9k |
| :8291 | Winbox MikroTik Admin | TCP | Security | caution | 62.9k |
| :3268 | Microsoft Global Catalog (GC) | TCPUDP | Security | caution | 54.6k |
| :135 | Microsoft EPMAP | TCPUDP | Security | caution | 51.9k |
| :3128 | Squid Proxy HTTP | TCP | Web Services | caution | 45.8k |
| :8080 | HTTP Alternate | TCPtls | Web Services | caution | 44.9k |
| :7000 | Vuze HTTPS Tracker | TCPtls | Security | caution | 28.9k |
risk mix of the 8 listed
- caution100%
3 of 8 encrypted