Cameradar alternatives and similar packages
Based on the "Security" category.
Alternatively, view Cameradar alternatives based on common mentions on social networks and blogs.
Lean and Mean Docker containersSlim(toolkit): Don't change anything in your container image and minify it by up to 30x (and for compiled languages even more) making it secure too! (free and open source)
age9.7 7.3 Cameradar VS ageA simple, modern and secure encryption tool (and Go library) with small explicit keys, no config options, and UNIX-style composability.
lego9.4 6.3 Cameradar VS legoLet's Encrypt/ACME client and library written in Go
autocert9.1 4.3 Cameradar VS autocert[mirror] Go supplementary cryptography libraries
CertMagic9.0 7.0 Cameradar VS CertMagicAutomatic HTTPS for any Go program: fully-managed TLS certificate issuance and renewal
memguard8.3 2.1 Cameradar VS memguardSecure software enclave for storage of sensitive information in memory.
secure8.2 6.4 Cameradar VS secureHTTP middleware for Go that facilitates some quick security wins.
acmetool8.2 0.0 Cameradar VS acmetool:lock: acmetool, an automatic certificate acquisition tool for ACME (Let's Encrypt)
Themis by Cossack Labs8.0 8.3 L3 Cameradar VS Themis by Cossack LabsEasy to use cryptographic framework for data protection: secure messaging with forward secrecy and secure data storage. Has unified APIs across 14 platforms.
acra7.7 6.1 Cameradar VS acraDatabase security suite. Database proxy with field-level encryption, search through encrypted data, SQL injections prevention, intrusion detection, honeypots. Supports client-side and proxy-side ("transparent") encryption. SQL, NoSQL.
Coraza7.6 7.4 Cameradar VS CorazaOWASP Coraza WAF is a golang modsecurity compatible web application firewall library
ToRat7.5 0.0 Cameradar VS ToRatToRat is a Remote Administation tool written in Go using Tor as a transport mechanism and RPC for communication
dongle7.0 1.3 Cameradar VS dongleA simple, semantic and developer-friendly golang package for encoding&decoding and encryption&decryption
nacl6.6 0.0 Cameradar VS naclPure Go implementation of the NaCL set of API's
go-yara6.4 0.0 Cameradar VS go-yaraGo bindings for YARA
go-password-validatorValidate the Strength of a Password in Go
booster6.1 7.2 Cameradar VS boosterFast and secure initramfs generator
ssh-vault6.1 0.0 Cameradar VS ssh-vault🌰 encrypt/decrypt using ssh keys
optimus-go5.9 0.0 Cameradar VS optimus-goID hashing and Obfuscation using Knuth's Algorithm
firewalld-rest5.9 0.0 Cameradar VS firewalld-restA rest application to update firewalld rules on a linux server
passlib5.8 0.0 Cameradar VS passlib:key: Idiotproof golang password validation library inspired by Python's passlib
BadActor5.8 0.0 Cameradar VS BadActorBadActor.org An in-memory application driven jailer written in Go
bitwarden-go5.6 0.0 Cameradar VS bitwarden-goA Bitwarden-compatible server written in Golang
simple-scrypt5.2 0.0 Cameradar VS simple-scryptA convenience library for generating, comparing and inspecting password hashes using the scrypt KDF in Go 🔑
teler-waf4.9 9.1 Cameradar VS teler-wafteler-waf is a Go HTTP middleware that provides teler IDS functionality to protect against web-based attacks.
argon2pw4.0 0.0 Cameradar VS argon2pwArgon2 password hashing package for go with constant time hash comparison
goSecretBoxPassword3.3 0.0 Cameradar VS goSecretBoxPasswordA probably paranoid Golang utility library for securely hashing and encrypting passwords based on the Dropbox method. This implementation uses Blake2b, Scrypt and XSalsa20-Poly1305 (via NaCl SecretBox) to create secure password hashes that are also encrypted using a master passphrase.
go-generate-passwordPassword generator written in Go
certificates2.7 0.0 Cameradar VS certificatesAn opinionated helper for generating tls certificates
go-htpasswd2.7 0.0 Cameradar VS go-htpasswdApache htpasswd Parser for Go.
Credman2.5 0.0 Cameradar VS CredmanSimple and secure credential/password management with extra steps in Go!
secureio2.4 0.0 Cameradar VS secureioAn easy-to-use XChaCha20-encryption wrapper for io.ReadWriteCloser (even lossy UDP) using ECDH key exchange algorithm, ED25519 signatures and Blake3+Poly1305 checksums/message-authentication for Go (golang). Also a multiplexer.
sslmgr2.0 0.0 Cameradar VS sslmgrA layer of abstraction the around acme/autocert certificate manager (Golang)
goArgonPass2.0 0.0 Cameradar VS goArgonPassgoArgonPass is a Argon2 Password utility package for Go using the crypto library package Argon2 designed to be compatible with Passlib for Python and Argon2 PHP. Argon2 was the winner of the most recent Password Hashing Competition. This is designed for use anywhere password hashing and verification might be needed and is intended to replace implementations using bcrypt or Scrypt.
garble1.9 6.1 Cameradar VS garble*fork* of https://github.com/burrowers/garble
go-acl1.9 0.0 Cameradar VS go-aclGo support for Access Control Lists
argon2-hashing1.9 0.0 Cameradar VS argon2-hashingA light package for generating and comparing password hashing with argon2 in Go
secret1.8 0.0 Cameradar VS secretPrevent your secrets from leaking into logs, std* etc.
ACL0.7 0.0 Cameradar VS ACLA simple but powerful Access Control List manager
Go random string generatorFlexible and customizable random string generator
InterpolRule-based data generator for fuzzing and penetration testing.
Clean code begins in your IDE with SonarLint
* Code Quality Rankings and insights are calculated and provided by Lumnify.
They vary from L1 to L5 with "L5" being the highest.
Do you think we are missing an alternative of Cameradar or a related project?
An RTSP stream access tool that comes with its library
Cameradar allows you to
- Detect open RTSP hosts on any accessible target host
- Detect which device model is streaming
- Launch automated dictionary attacks to get their stream route (e.g.:
- Launch automated dictionary attacks to get the username and password of the cameras
- Retrieve a complete and user-friendly report of the results
Table of content
- Docker Image
- Check camera access
- Command-line options
- Frequently Asked Questions
Docker Image for Cameradar
Install docker on your machine, and run the following command:
docker run -t ullaakut/cameradar -t <target> <other command-line options>
docker run -t ullaakut/cameradar -t 192.168.100.0/24 will scan the ports 554, 5554 and 8554 of hosts on the 192.168.100.0/24 subnetwork and attack the discovered RTSP streams and will output debug logs.
YOUR_TARGETcan be a subnet (e.g.:
172.16.100.0/24), an IP (e.g.:
172.16.100.10), or a range of IPs (e.g.:
- If you want to get the precise results of the nmap scan in the form of an XML file, you can add
-v /your/path:/tmp/cameradar_scan.xmlto the docker run command, before
- If you use the
-coptions to specify your custom dictionaries, make sure to also use a volume to add them to the docker container. Example:
docker run -t -v /path/to/dictionaries/:/tmp/ ullaakut/cameradar -r /tmp/myroutes -c /tmp/mycredentials.json -t mytarget
Installing the binary on your machine
Only use this solution if for some reason using docker is not an option for you or if you want to locally build Cameradar on your machine.
WARNING: Manually building the binary will NOT WORK for any camera that uses DIGEST AUTHENTICATION if your version of
curl is over
7.64.0, which is most likely the case. For more information, see this response on the subject from the author of curl.
libcurldevelopment library (version has to be <7.66.0)
- For apt users:
apt install libcurl4-openssl-dev
- For apt users:
Steps to install
go install github.com/Ullaakut/cameradar/v5/cmd/[email protected]
cameradar binary is now in your
$GOPATH/bin ready to be used. See command line options here.
The RTSP port used for most cameras is 554, so you should probably specify 554 as one of the ports you scan. Not specifying any ports to the cameradar application will scan the 554, 5554 and 8554 ports.
docker run -t --net=host ullaakut/cameradar -p "18554,19000-19010" -t localhost will scan the ports
18554, and the range of ports between
You can use your own files for the credentials and routes dictionaries used to attack the cameras, but the Cameradar repository already gives you a good base that works with most cameras, in the
docker run -t -v /my/folder/with/dictionaries:/tmp/dictionaries \ ullaakut/cameradar \ -r "/tmp/dictionaries/my_routes" \ -c "/tmp/dictionaries/my_credentials.json" \ -t 172.19.124.0/24
This will put the contents of your folder containing dictionaries in the docker image and will use it for the dictionary attack instead of the default dictionaries provided in the cameradar repo.
Check camera access
If you have VLC Media Player, you should be able to use the GUI or the command-line to connect to the RTSP stream using this format:
- "-t, --targets": Set target. Required. Target can be a file (see instructions on how to format the file), an IP, an IP range, a subnetwork, or a combination of those. Example:
- "-p, --ports": (Default:
554,5554,8554) Set custom ports.
- "-s, --scan-speed": (Default:
4) Set custom nmap discovery presets to improve speed or accuracy. It's recommended to lower it if you are attempting to scan an unstable and slow network, or to increase it if on a very performant and reliable network. You might also want to keep it low to keep your discovery stealthy. See this for more info on the nmap timing templates.
- "-I, --attack-interval": (Default:
0ms) Set custom interval after which an attack attempt without an answer should give up. It's recommended to increase it when attempting to scan unstable and slow networks or to decrease it on fast and reliable networks.
- "-T, --timeout": (Default:
2000ms) Set custom timeout value after which an attack attempt without an answer should give up. It's recommended to increase it when attempting to scan unstable and slow networks or to decrease it on fast and reliable networks.
- "-r, --custom-routes": (Default:
<CAMERADAR_GOPATH>/dictionaries/routes) Set custom dictionary path for routes
- "-c, --custom-credentials": (Default:
<CAMERADAR_GOPATH>/dictionaries/credentials.json) Set custom dictionary path for credentials
- "-o, --nmap-output": (Default:
/tmp/cameradar_scan.xml) Set custom nmap output path
- "-d, --debug": Enable debug logs
- "-v, --verbose": Enable verbose curl logs (not recommended for most use)
- "-h": Display the usage information
Format input file
The file can contain IPs, hostnames, IP ranges and subnetwork, separated by newlines. Example:
0.0.0.0 localhost 18.104.22.168/16 192.168.1.140-255 192.168.2-3.0-255
This variable is mandatory and specifies the target that cameradar should scan and attempt to access RTSP streams on.
This variable is optional and allows you to specify the ports on which to run the scans.
It is recommended not to change these except if you are certain that cameras have been configured to stream RTSP over a different port. 99.9% of cameras are streaming on these ports.
This variable is optional and allows you to specify on which file nmap will write its output.
This can be useful only if you want to read the files yourself, if you don't want it to write in your
/tmp folder, or if you want to use only the RunNmap function in cameradar, and do its parsing manually.
These variables are optional, allowing to replace the default dictionaries with custom ones, for the dictionary attack.
This optional variable allows you to set custom nmap discovery presets to improve speed or accuracy. It's recommended to lower it if you are attempting to scan an unstable and slow network, or to increase it if on a fast and reliable network. See this for more info on the nmap timing templates.
This optional variable allows you to set
custom interval to wait between each attack in order to stay stealthy. It's recommended to increase it when attempting to scan a network that might be protected against bruteforce attacks. By default, there is no interval, in order to make attacks as fast as possible
This optional variable allows you to set custom timeout value after which an attack attempt without an answer should give up. It's recommended to increase it when attempting to scan unstable and slow networks or to decrease it on fast and reliable networks.
This optional variable allows you to enable a more verbose output to have more information about what is going on.
It will output nmap results, cURL requests, etc.
To build the docker image, simply run
docker build . -t cameradar in the root of the project.
Your image will be called
cameradar and NOT
go get github.com/Ullaakut/cameradar
The cameradar binary is now in
Frequently Asked Questions
Cameradar does not detect any camera!
That means that either your cameras are not streaming in RTSP or that they are not on the target you are scanning. In most cases, CCTV cameras will be on a private subnetwork, isolated from the internet. Use the
-t option to specify your target. If you are sure you did everything right but it still does not work, please open an issue with details on the device you are trying to access 🙏
Cameradar detects my cameras, but does not manage to access them at all!
Maybe your cameras have been configured, and the credentials / URL have been changed. Cameradar only guesses using default constructor values if a custom dictionary is not provided. You can use your own dictionaries in which you just have to add your credentials and RTSP routes. To do that, see how the configuration works. Also, maybe your camera's credentials are not yet known, in which case if you find them it would be very nice to add them to the Cameradar dictionaries to help other people in the future.
What happened to the C++ version?
You can still find it under the 1.1.4 tag on this repo, however it was slower and less stable than the current version written in Golang. It is not recommended using it.
How to use the Cameradar library for my own project?
See the example in
/cmd/cameradar. You just need to run
go get github.com/Ullaakut/cameradar and to use the
cameradar package in your code. You can find the documentation on godoc.
I want to scan my own localhost for some reason, and it does not work! What's going on?
--net=host flag when launching the cameradar image, or use the binary by running
go run cameradar/cameradar.go or installing it.
I don't see a colored output:(
You forgot the
-t flag before
ullaakut/cameradar in your command-line. This tells docker to allocate a pseudo-tty for cameradar, which makes it able to use colors.
I don't have a camera, but I'd like to try Cameradar!
docker run -p 8554:8554 -e RTSP_USERNAME=admin -e RTSP_PASSWORD=12345 -e RTSP_PORT=8554 ullaakut/rtspatt and then run cameradar, and it should guess that the username is admin and that the password is 12345. You can try this with any default constructor credentials (they can be found [here](dictionaries/credentials.json)).
What authentication types does Cameradar support?
Cameradar supports both basic and digest authentication.
Running cameradar on your own machine to scan for default ports
docker run --net=host -t ullaakut/cameradar -t localhost
Running cameradar with an input file, logs enabled on port 8554
docker run -v /tmp:/tmp --net=host -t ullaakut/cameradar -t /tmp/test.txt -p 8554
Running cameradar on a subnetwork with custom dictionaries, on ports 554, 5554 and 8554
docker run -v /tmp:/tmp --net=host -t ullaakut/cameradar -t 192.168.0.0/24 --custom-credentials="/tmp/dictionaries/credentials.json" --custom-routes="/tmp/dictionaries/routes" -p 554,5554,8554
Copyright 2019 Ullaakut
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
*Note that all licence references and agreements mentioned in the Cameradar README section above are relevant to that project's source code only.