Quantcast
Channel: Hackers Online Club (HOC)
Viewing all 855 articles
Browse latest View live

Top 6 Ways To Speed Up Your Mobile Device

$
0
0

Top 6 Ways To Speed Up Your Mobile Device

As much as you use your smartphone over time, it keeps slowing down and the reason behind that may be you probably have too many apps installed in your smartphone. There are many apps which runs in background and consumes a lot of memory and power of your mobile device. So following tips might be useful to increase the memory of your smartphone and help increase your mobile speed too.

1. Uninstall unused Apps

There could be many apps which you might not be using for a while, or its pre-installed with your smartphone. The easiest way to increase your phone storage would be to remove them.

-> Go to your Mobile Settings
-> Tap on App, select App which you would like to Uninstall
-> Also you can use Force stop and clear the cache Data to speed up your device.


2. Clean up your Device Storage

Poor Internal Storage can affect the smartphone performance too. You can remove the data like music, videos which you rarely use. Also remove WhatsApp videos and images which were downloaded automatically at the time of watching it. So keep trying to save up your phone memory as much as you can.

3. Monitor those Apps which are consuming your smartphone Power.

Some apps runs in the background, so just follow these steps:

-> Go to Settings
-> Tap on Battery
-> Check ununusal app and hit force to remove it from the background processes.

Here you can check all of your Apps which consumes a lot of battery percentage wise.

Also use Settings > Apps or Apps Manager to find out which apps are consuming most of the RAM.



4. Remove Widgets

In Smartphones, widgets are the main reason to slow down your devices. So try to reduce your widgets usage as much as possible. Do not use any live animated wallpaper, it affects your phone memory and battery.

5. Always Keep your Smartphone updated

Smartphone software update is important,

Go to Mobile Settings
Tap on System updates
Tap on Check updates,
Tap on Install,
and Reboot your Device.

6. Factory Reset of your Smartphone

If your device is still not giving good performance then you can perform a factory data reset.
You can erase the complete data from your Android phone or tablet by resetting it to factory settings. Resetting this way is also called "formatting," or a "hard reset."

Open your device's Settings app,
Tap on System and then Reset.  If needed, enter your PIN, pattern, or password.
Note: If your settings are different, tap on Backup & reset.
Tap on Factory data reset and then tap on Reset phone or Reset tablet. If needed, enter your PIN, pattern, or password.
To erase all data from your device's internal storage, tap on Erase everything.
When your device has finished erasing, choose an option to restart.
Set up your device and restore your backed-up data.


Kali Linux Operating System New Version 2018.1 Released With Increase Memory Limits

$
0
0
Kali Linux Operating System New Version 2018.1 Released With Increase Memory Limits


Kali Linux Operating System New Version 2018.1 Released With Increase Memory Limits



According to update, this release contains all updated packages and bug fixes since our 2017.3 release last November. This release wasn’t without its challenges– from the Meltdown and Spectre excitement (patches will be in the 4.15 kernel) to a couple of other nasty bugs, we had our work cut out for us but we prevailed in time to deliver this latest and greatest version for your installation pleasure.

Kernel Updated to 4.14

Kali Linux 2018.1 has a shiny new 4.14.12 kernel. New kernels always have a lot of new features and the 4.14 kernel is no exception, although two new features really stand out.

AMD Secure Memory Encryption Support – 

Secure Memory Encryption is a feature that will be in newer AMD processors that enables automatic encryption and decryption of DRAM. The addition of this features means that systems will no longer (in theory) be vulnerable to cold-boot attacks because, even with physical access, the memory will be not be readable.

Increased Memory Limits – 

Current (and older) 64-bit processors have a limit of 64 TB of physical address space and 256 TB of virtual address space (VAS), which was sufficient for more than a decade but with some server hardware shipping with 64 TB of memory, the limits have been reached. Fortunately, upcoming processors will enable 5-level paging, support for which is included in the 4.14 kernel. In short, this means that these new processors will support 4 PB of physical memory and 128 PB of virtual memory. That’s right, petabytes.

Package Updates

In addition to the updated kernel, we have also upgraded a number of packages, including zaproxy, secure-socket-funneling, pixiewps, seclists, burpsuite, dbeaver, and reaver. If you already have a Kali installation, you can easily get the latest version of these tools along with everything else that has been updated:

apt update && apt full-upgrade

Note that if you haven’t updated your Kali installation in some time (tsk2), you will like receive a GPG error about the repository key being expired (ED444FF07D8D0BF6). Fortunately, this issue is quickly resolved by running the following as root:

wget -q -O - https://archive.kali.org/archive-key.asc | apt-key add

Hyper-V Updates

For those of you using Hyper-V to run the Kali virtual machines provided by Offensive Security, you will find that the Hyper-V virtual machine is now generation 2, which means it’s now UEFI-based and expanding/shrinking HDD is supported. The Hyper-V integration services are also included, which supports Dynamic Memory, Network Monitoring/Scaling, and Replication.

As always, you can Download Latest Kali Linux ethical hacking and penetration testing operating system from its official website, where you will also find links to the pre-made virtual machines and ARM images provided by Offensive Security.

If you encounter any bugs with this, or any other, release, please don’t suffer in silence and open a report on the Kali Bug Tracker so we can investigate and fix it.

How This Indian Language Character Can Crash Your iPhone and Mac

$
0
0
How This Indian Language Character Can Crash Your iPhone and Mac


How this simple Indian Language Character Can Crash Your iPhone and MacOS devices


Hackersonlineclub (HOC) has tried testing the code at the time of writing this article but we were not been able to reproduce any crashes but found that iOS device was slowing down while opening an email which contains this character.


This character affects iMessage, Facebook and WhatsApp apps. Even if it is just pasted on Chrome or Safari browser, it gets crashed.

For example, if that character is being sent to your iMessage, it can crash your messaging app across Mac and iOS devices.

The impact of this issue is still there on certain apps running on latest version of iOS, macOS and watchOS. Some of the users were also complaint that Twitter app is also affected in the Apple devices.

According to Mobileworld,

If the character is displayed within an application (WhatsApp, Twitter, etc.), the app in question will crash and will continue to close each time you try to start it. The situation gets worse if someone sends you the symbol and iOS tries to show it in a notification : in this case, the entire Springboard (i.e. the system software that manages the Home) crashes.

If this happens, wait and hope that the Springboard will restart properly, because if you force a reboot of the device, it will bootloop.

Currenty, Apple is facing many security issues and bugs. If your iOS device is still affected with this issue then just go to this link here and upgrade to iOS 11.3 or macOS 10.13.4.

Security Alert! Your Mac is Spying on You

$
0
0
Security Alert! Your Mac is Spying on You


Security Alert! Your Mac is Spying on You

Sandboxed Mac apps can record your screen at any time without your knowledge.

According to security expert, Felix Krause explain in the blog. The third party apps can spy on everything that you are working on MAC. These malicious app is running in the background and there is no alert when it takes Snapshot.

Facts

Any Mac app, sandboxed or not sandboxed can:

  • Take screenshots of your Mac silently without you knowing
  • Access every pixel, even if the Mac app is in the background
  • Use basic Optical Character Recognition (OCR) software to read the text on the screen
  • Access all connected monitors
  • What’s the worst that could happen?
  • Read password and keys from password managers
  • Detect what web services you use (e.g. email provider)
  • Read all emails and messages you open on your Mac
  • When a developer is targeted, this allows the attacker to potentially access sensitive source code, API keys or similar data
  • Learn personal information about the user, like their bank details, salary, address, etc.

Proposal

There are lots of valid use-cases for Mac apps to record the screen, e.g. 1Password 2fA support, screen recording software or even simple screen sharing via your web browser or Skype. However there must be some kind of control:

  • The App Store review process could verify the Sandbox entitlements for accessing the screen
  • Put the user in charge with a permission dialog
  • Additionally the user should be notified whenever an app accesses the screen.

How does it work?

A developer just needs to use CGWindowListCreateImage to generate a capture of the complete screen within an instant:

CGImageRef screenshot = CGWindowListCreateImage(
  CGRectInfinite, 
  kCGWindowListOptionOnScreenOnly, 
  kCGNullWindowID, 
  kCGWindowImageDefault);

NSBitmapImageRep *bitmapRep = [[NSBitmapImageRep alloc] initWithCGImage:screenshot];

How to Fix?

There is no way that you block these malicious apps. Only Apple will have to be fixed the issue.

Striker: An Offensive Information And Vulnerability Scanner

$
0
0


Striker is an offensive information and vulnerability scanner.


Features

Just supply a domain name to Striker and it will automatically do the following for you:

  •  Check and Bypass Cloudflare
  •  Retrieve Server and Powered by Headers
  •  Fingerprint the operating system of Web Server
  •  Detect CMS (197+ CMSs are supported)
  •  Launch WPScan if target is using Wordpress
  •  Retrieve robots.txt
  •  Whois lookup
  •  Check if the target is a honeypot
  •  Port Scan with banner grabbing
  •  Dumps all kind of DNS records
  •  Generate a map for visualizing the attack surface
  •  Gather Emails related to the target
  •  Find websites hosted on the same web server
  •  Find hosts using google
  •  Crawl the website for URLs having parameters
  •  SQLi scan using online implemention of SQLMap (takes < 3 min.)
  •  Basic XSS scanning


Install

git clone https://github.com/UltimateHackers/Striker
cd Striker
pip install -r requirements.txt
python striker.py

Screenshots


Download Striker

Punjab National Bank (PNB) Credit and Debit Card Data Breached

$
0
0
Punjab National Bank (PNB) Credit and Debit Card Data Breached

Punjab National Bank (PNB)'s Sensitive Information of 10,000 Credit and Debit Card Data Breached


The leaked information includes Names, Personal Identification Numbers (PIN), Expiry Dates and card verification values online.


Credit and debit cards details  are selling on Darkweb websites. Darkweb is illegally selling underground services such as Hacking or other leaked information.

Firstly CloudSek team identified a listing that claimed to have multiple cards that belonged to PNB that were put up for sale on a DarkWeb site. "We immediately tried reaching out to PNB using the cybercrime contact emails that were listed on their website. But that email bounced. said Rahul Sasi, CTO of Cloudsek.

On 21st, Feb, 8:10 PM company was able to get in touch with PNB officials via a third party source. The PNB officials were quick to respond as they got a call back the same day at 10.00 PM from PNB security officials. We provided them a detailed report about the leaked data.

On 22nd, Feb, 1:10 AM we provided them a more detailed report. And the officials ensured swift action."

According to report of Atimes,

“We believe, on preliminary analysis, that the data has been available for at least three months. While this is yet to be firmly established, we are carrying out our forensic investigation,” said a government official familiar with the case. Virwani was asked by Asia Times to comment on the breach, but has not yet responded. A message received from him states that he was not authorized to respond to the media and the queries have been forwarded to the Corporate Communications department. The story will be updated as and when a response is received.

“Usually these sites on the deep/dark web build up reputations on the authenticity of the data they sell illegally. This particular site has a very good reputation. They offer a sample size to buyers to establish their credentials before the sale is made. In this case they were offering to sell the data at US$4.90 per card,” he reported

PNB is already suffering from the latest fraud case worth 11,400 Crore in Indian Rupees. The firms were unable to pay to Bank after their bank accounts were frozen by the ED and the CBI in connection with the alleged Rs 11,400-crore scam.

In India, there are still some Banks and ATM's running on Windows XP, however support for Windows XP ended on 8 April 2014. Microsoft will no longer provide security updates or technical support for the Windows XP operating system. It is very important that customers and partners migrate to a modern operating system such as latest Microsoft Operating System Windows 10.

Tunna: A Set of Tools Which Will Wrap And Tunnel Any TCP Communication Over HTTP

$
0
0
Tunna: A Set of Tools Which Will Wrap And Tunnel Any TCP Communication Over HTTP


Tunna: A Set of Tools Which Will Wrap And Tunnel Any TCP Communication Over HTTP

It can be used to bypass network restrictions in fully firewalled environments.


SUMMARY

TLDR: Tunnels TCP connections over HTTP

In a fully firewalled (inbound and outbound connections restricted - except the webserver port)

The webshell can be used to connect to any service on the remote host. This would be a local connection on a local port at the remote host and should be allowed by the firewall.

The webshell will read data from the service port wrap them over HTTP and send it as an HTTP response to the local proxy.

The local proxy will unwrap and write the data to it's local port where the client program would be connected.

When the local proxy receives data on the local port, it will send them over to the webshell as an HTTP Post.

The webshell will read the data from the HTTP Post and put them on the service port

and repeat Only the webserver port needs to be open (typically 80/443) The whole communication (Externally) is done over the HTTP protocol.

USAGE

python proxy.py -u <remoteurl> -l <localport> [options]

Options

--help, -h show this help message and exit

--url=URL, -u URL url of the remote webshell

--lport=LOCAL_PORT, -l LOCAL_PORT local listening port

--verbose, -v Verbose (outputs packet size)

--buffer=BUFFERSIZE, -b BUFFERSIZE* HTTP request size (some webshels have limitations on the size)

No SOCKS Options

Options are ignored if SOCKS proxy is used

--no-socks, -n Do not use Socks Proxy

--rport=REMOTE_PORT, -rREMOTE_PORT remote port of service for the webshell to connect to

--addr=REMOTE_IP, -a REMOTE_IP address for remote webshell to connect to (default = 127.0.0.1)

Upstream Proxy Options

Tunnel connection through a local Proxy

--up-proxy=UPPROXY, -x UPPROXY Upstream proxy (http://proxyserver.com:3128)

--auth, -A Upstream proxy requires authentication

Advanced Options

--ping-interval=PING_DELAY, -q PING_DELAY webshprx pinging thread interval (default = 0.5)

--start-ping, -s Start the pinging thread first - some services send data first (eg. SSH)

--cookie, -C Request cookies

--authentication, -t Basic authentication

See limitations

Example usage:python proxy.py -u http://10.3.3.1/conn.aspx -l 8000 -v

# This will start a Local SOCKS Proxy Server at port 80000
# This connection will be wrapped over HTTP and unwrapped at the remote server

python proxy.py -u http://10.3.3.1/conn.aspx -l 8000 -x https://192.168.1.100:3128 -A -v

# This will start a Local SOCKS Proxy Server at port 80000
# It will connect through a Local Proxy (https://192.168.1.100:3128) that requires authentication
# to the remote Tunna webshell

python proxy.py -u http://10.3.3.1/conn.aspx -l 4444 -r 3389 -b 8192 -v --no-socks

# This will initiate a connection between the webshell and Remote host RDP (3389) service
# The RDP client can connect on localhost port 4444
# This connection will be wrapped over HTTP

Prerequisites

The ability to upload a webshell on the remote server
LIMITATIONS / KNOWN BUGS / HACKS
This is a POC code and might cause DoS of the server.
All efforts to clean up after execution or on error have been made (no promises)

Based on local tests:
* JSP buffer needs to be limited (buffer option):
4096 worked in Linux Apache Tomcat
1024 worked in XAMPP Apache Tomcat (slow)
* More than that created problems with bytes missing at the remote socket
eg: ruby proxy.rb -u http://10.3.3.1/conn.jsp -l 4444 -r 3389 -b 1024 -v

* Sockets not enabled by default php windows (IIS + PHP)

* Return cariages on webshells (outside the code):
get sent on responses / get written on local socket --> corrupt the packets

* PHP webshell for windows: the loop function DoS'es the remote socket:
sleep function added -> works but a bit slow
* PHP webshell needs new line characters removed at the end of the file (after "?>")
as these will get send in every response and confuse Tunna

FILES

Webshells:

conn.jspTested on Apache Tomcat (windows + linux)
conn.aspxTested on IIS 6+8 (windows server 2003/2012)
conn.phpTested on LAMP + XAMPP + IIS (windows + linux)

WebServer:

webserver.pyTested with Python 2.6.5

Proxies:

proxy.pyTested with Python 2.6.5

Technical Details

Architecture descisions
Data is sent raw in the HTTP Post Body (no post variable)

Instructions / configuration is sent to the webshell as URL parameters (HTTP Get)
Data is sent in the HTTP body (HTTP Post)

Websockets not used: Not supported by default by most of webservers
Asyncronous HTTP responses not really possible
  • Proxy queries the server constantly (default 0.5 seconds)

INITIATION PHASE

1st packet initiates a session with the webshell - gets a cookie back eg: http://webserver/conn.ext?proxy

2nd packet sends connection configuration options to the webshell eg: http://webserver/conn.ext?proxy&port=4444&ip=127.0.0.1

IP and port for the webshell to connect to
This is a threaded request:
  • In php this request will go into an infinate loop 
  • to keep the webshell socket connection alive
  • In other webshells [OK] is received back


TUNNA CLIENT

A local socket is going to get created where the client program is going to connect to Once the client is connected the pinging thread is initiated and execution starts. Any data on the socket (from the client) get read and get sent as a HTTP Post request Any data on the webshell socket get sent as a response to the POST request.

PINGING THREAD

Because HTTP responses cannot be asyncronous. This thread will do HTTP Get requests on the webshell based on an interval (default 0.5 sec) If the webshell has data to send, it will (also) send it as a reply to this request Otherwise it sends an empty response.

In general: Data from the local proxy get send with HTTP Post There are Get requests every 0.5 sec to query the webshell for data If there is data on the webshell side get send over as a response to one of these requests.

WEBSHELL

The webshell connects to a socket on the local or a remote host. Any data written on the socket get sent back to the proxy as a reply to a request (POST/GET) Any data received with a post get written to the socket.

NOTES
All requests need to have the URL parameter "proxy" set to be handled by the webshell (http://webserver/conn.ext?proxy)

AT EXIT / AT ERROR
Kills all threads and closes local socket Sends proxy&close to webshell: Kills remote threads and closes socket

SOCKS
The SOCKS support is an addon module for Tunna. Locally is a seperate thread that handles the connection requests and traffic adds a header that specifies the port and the size of the packet and forwards it to Tunna. Tunna sends it over to the remote webserver, removes the HTTP headers and forwards the packet to the remote SOCKS proxy.

The remote SOCKS proxy initiates the connection and mapps the received port to the local port. If the remote SOCKS proxy receives data from the service, it looks at the mapping table and finds the port it needs to respond to, adds the port as a header so the local SOCKS proxy will know where to forward the data. Any traffic from the received port will be forwarded to the local port and vice versa.

Download Tunna

BootStomp: An Android boot-loader Bug Finder

$
0
0
BootStomp: An Android boot-loader Bug Finder


BootStomp: An Android boot-loader Bug Finder


To run BootStomp's analyses, please read the following instructions. Note that BootStomp works with boot-loaders compiled for ARM architectures (32 and 64 bits both) and that results might slightly vary depending on angr and Z3's versions. This is because of the time angr takes to analyze basic blocks and to Z3's expression concretization results.

It looks for two different class of bugs: memory corruption and state storage vulnerabilities. For more info please refer to the BootStomp paper at https://seclab.cs.ucsb.edu/academic/publishing/#bootstomp-security-bootloaders-mobile-devices-2017

How does BootStomp find Android Vulnerabilities?

BootStomp implements a multi-tag taint analysis resulting from a novel combination of static analyses and dynamic symbolic execution, designed to locate problematic areas where input from an attacker in control of the OS can compromise the bootloader’s execution or its security features.

Using the tool the team found six previously-unknown vulnerabilities (of which five have been confirmed by the respective vendors), as well as rediscovered one that had been previously reported. Some of these vulnerabilities would allow an attacker to execute arbitrary code as part of the bootloader (thus compromising the entire chain of trust), or to perform permanent denial-of-service attacks.

The team analyzed bootloader implementations in many platforms, including Huawei P8 ALE-L23 (Huawei / HiSilicon chipset), Sony Xperia XA (MediaTek chipset), Nexus 9 (NVIDIA Tegra chipset), and two versions of the LK-based bootloader (Qualcomm).

Directory structure

analysis: Contains analysis results (Ex: IDA idbs etc) of boot images of different devices.
tools: Contains tools that can be used to work with various images.

Pre-requisites

angr (http://angr.io/)
$ pip install angr


  • IDA PRO (https://www.hex-rays.com/products/ida/)
  • IDA Decompiler (https://www.hex-rays.com/products/decompiler/)

How to run it?

Run BootStomp using docker

The easiest way to use BootStomp is to run it in a docker container. The folder docker contains an appropriate Dockerfile. These are the commands to use it.

cd docker
# build the docker image
docker build -t bootstomp .
# run the docker image (if you need, use proper options to have persistent changes or shared files)
docker run -it bootstomp

# now you are inside a docker container
cd BootStomp
# run BootStomp's taint analysis on one of the examples
# this will take about 30 minutes
python taint_analysis/bootloadertaint.py config/config.huawei
# the last line of the output will be something like:
# INFO    | 2017-10-14 01:54:10,617 | _CoreTaint | Results in /tmp/BootloaderTaint_fastboot.img_.out

# you can then "pretty print" the results using:
python taint_analysis/result_pretty_print.py /tmp/BootloaderTaint_fastboot.img_.out

The output should be something like this:

17)
===================== Start Info path =====================
Dereference address at: 0x5319cL
Reason: at location 0x5319cL a tainted variable is dereferenced and used as address.
...
Tainted Path 
----------------
0x52f3cL -> 0x52f78L -> 0x52f8cL -> 0x52fb8L -> 0x52fc8L -> 0x52fecL -> 0x53000L -> 0x53014L -> 0x5301cL -> 0x53030L -> 0x53044L -> 0x53050L -> 0x5305cL -> 0x53068L
===================== End Info path =====================
# Total sinks related alerts: 5
# Total loop related alerts: 8
# Total dereference related alerts: 4

Run BootStomp manually

Automatic detection of taint sources and sinks

  1. Load the boot-loader binary in IDA (we used v6.95). Depending on the CPU architecture of the phone it has been extracted from, 32 bit or 64 bit IDA is needed.
  2. From the menu-bar, run File => Script file => find_taint.py
  3. Output will appear in the file taint_source_sink.txt under the same directory as the boot-loader itself.

Configuration file


Create a JSON configuration file for the boot-loader binary (see examples in config/), where:

bootloader: boot-loader file path
info_path: boot-loader source/sink info file path (i.e., taint_source_sink.txt )
arch: architecture's number of bits (available options are 32 and 64)
enable_thumb: consider thumb mode (when needed) during the analysis
start_with_thumb: starts the analysis with thumb mode enabled
exit_on_dec_error: stop the analysis if some instructions cannot be decoded
unlock_addr: unlocking function address. This field is necessary only for finding insecure state storage vulnerabilities.

Finding memory corruption vulnerabilities

Run

python bootloadertaint.py config-file-path

Results will be stored in /tmp/BootloaderTaint_[boot-loader].out, where [boot-loader] is the name of the analyzed boot-loader. Note that paths involving loops might appear more than once.

Finding insecure state storage vulnerability
Run

python unlock_checker.py config-file-path

Results will be stored in /tmp/UnlockChecker_[boot-loader].out, where [boot-loader] is the name of the analyzed boot-loader. Note that paths involving loops might appear more than once.

Checking results

To check BootStomp results, use the script result_pretty_print.py, as follows:

python result_pretty_print.py results_file

Download

Google Chrome 65 Released For Mac, Windows And Linux OS With New Security Features

$
0
0
Google Chrome 65 Update


Google Chrome 65 Released For Mac, Windows And Linux OS With New Security Features.

Chrome 65.0.3325.146 contains a number of fixes and improvements.


The Chrome team is delighted to announce the promotion of Chrome 65 to the stable channel for Windows, Mac and Linux. This will roll out over the coming days/weeks.

Google is adding support for a Web Authentication API to allow the creation ans use of strong, attested, cryptographic scoped credentials by web Applications. This feature is to improve strong authenticating users. You can be enabled via flag.

The chrome browser now supports draft-23 of the TLS 1.3 protocol responsible for secure communication on the web.

New in Chrome 65 

CSS Paint API -

The CSS Paint API allows you to programmatically generate an image for CSS properties like background-image or border-image.

Instead of referencing an image, you can use the new paint function to draw the image - much like a canvas element.

<style>
  .myElem { background-image: paint(checkerboard); }
</style>
<script>
  CSS.paintWorklet.addModule('checkerboard.js');
</script>

For example, instead of adding extra DOM elements to create the ripple effect on a material styled button, you could use the paint API.

It’s also a powerful method of polyfilling CSS features that aren’t supported in a browser yet.

Server Timing API

Hopefully you’re using the navigation and resource timing APIs to track the performance of your site for real users. Until now, there hasn’t been an easy way for the server to report it’s performance timing.

The new Server Timing API allows your server to pass timing information to the browser; giving you a better picture of your overall performance.

You can track as many metrics as you want: database read times, start-up time, or whatever is important to you, by adding a Server-Timing header to your response:

'Server-Timing': 'su=42;"Start-up",db-read=142;"Database Read"'

They’re shown in Chrome DevTools, or you can pull them out of the response header and save them with your other performance analytics.

There are 45 security issues have been fixed including:


  • Flash errors
  • XSS in interstitials.
  • Mark-of-the-Web bypass. 
  • Heap buffer overflow in Skia
  • Stack buffer overflow in Skia
  • Same Origin Bypass via canvas.
  • CSP bypass through extensions.
  • URL Spoof in OmniBox.
  • Overly permissive cross origin downloads.
  • Information disclosure via texture data in WebGL.
  • Incorrect handling of URL fragment identifiers in Blink.


Google announces Chrome 64 for Android and Chrome OS will be available soon.

How To Remove Your Phone Number From TrueCaller?

$
0
0
How To Remove Your Phone Number From TrueCaller?

How To Remove Your Phone Number from TrueCaller?


Truecaller is a popular calling app, It shows you contact details of unknown number by calling you. Its grabbing your contact details from all its user phone address book. If you are using Truecaller or not, it doesn't matter, your name and number details might be in truecaller database. It can also list of your home address and it could be breached in your privacy.

So how can we remove your number from Truecaller database. If you are a Truecaller user and have verified your number you must first Deactivate your account by going to the Settings menu in the app.

Steps to Deactivate your TrueCaller account

For Android

Open the app > tap the people icon in the upper left corner > Settings > About > Deactivate account.

For iPhone

Open the app > tap the gear icon in the top right corner > About Truecaller > Scroll down > Deactivate Truecaller.

For Windows Mobile

Open the app and tap the three dots in the bottom right corner > Settings > Help > Deactivate account.

Once you have deactivated your Truecaller account, you can process to removing your number from the TrueCaller service.

How to Unlist Your Phone Number From TrueCaller?


If you don't want your number to be searchable in the Truecaller app, then enter your phone number below including the country code and click on 'Unlist'. (i.e. +4690512214).

Please note that it can take up to 24 hours before the number gets removed.

Go to this link to Unlist your Phone number
https://www.truecaller.com/unlisting

What is DNS Rebinding Attack? It's Work And Protection

$
0
0
What is DNS Rebinding Attack? It's Work And Protection


What is DNS Rebinding Attack? It's Work And Protection



What is DNS Rebinding Attack?

DNS rebinding is a form of computer attack or can say domain name computer based attack. In this attack, a malicious web page causes visitors to run a client-side script that attacks machines elsewhere on the network.

DNS rebinding attack can be used to breach a private network by causing the victim's web browser to access machines at private IP addresses and return the results to the attacker. It can also be employed to use the victim machine for spamming, distributed denial-of-service attacks or other malicious activities.

Cybercriminal can also do DNS rebinding attack through Malicious advertising and then they can access private information on the network.


How DNS rebinding works?

The attacker registers a domain (such as anydomain.com) and delegates it to a DNS server under the attacker's control. The server is configured to respond with a very short time to live (TTL) record, preventing the response from being cached. When the victim browses to the malicious domain, the attacker's DNS server first responds with the IP address of a server hosting the malicious client-side code.

For instance, they could point the victim's browser to a website that contains malicious JavaScript or Flash scripts that are intended to execute on the victim's computer.

The malicious client-side code makes additional accesses to the original domain name (such as attacker.com). These are permitted by the same-origin policy. However, when the victim's browser runs the script it makes a new DNS request for the domain, and the attacker replies with a new IP address. For instance, they could reply with an internal IP address or the IP address of a target somewhere else on the Internet.

How can we Protect Themselves?

The following techniques attempt to prevent DNS rebinding attacks:

  •  Always use a strong password for your router. 
  • To Disable admin access console to your router from any external network.
  • Web browsers can implement DNS pinning: the IP address is locked to the value received in the first DNS response. This technique may block some legitimate uses of Dynamic DNS, and may not work against all attacks. However, it is important to fail safe (stop rendering) if the IP address does change, because using an IP address past the TTL expiration can open the opposite vulnerability when the IP address has legitimately changed and the expired IP address may now be controlled by an attacker.
  • Private IP addresses can be filtered out of DNS responses.
  • External public DNS servers with this filtering e.g. OpenDNS.
  • Local sysadmins can configure the organization's local nameservers to block the resolution of external names into internal IP addresses. This has the downside of allowing an attacker to map the internal address ranges in use.
  • DNS filtering in a firewall or daemon e.g. dnswall.
  • Web servers can reject HTTP requests with an unrecognized Host header.
  • The Firefox NoScript extension provides partial protection (for private networks)
  • It was first discovered in 1996 and affected Java Virtual Machine.

Mac Calendar App Which Mines Cryptocurrency Removed From Apple Store

$
0
0
Mac Calendar App Which Mines Cryptocurrency Removed From Apple Store

Mac Calendar App Which Mines Cryptocurrency Removed From Apple Store



The Calender 2 App, it aims to include more features than the Apple calendar App bundle with macOS. The application is developed by Qbix. 


Currently it has removed from an official Mac App Store at itunes.apple.com/us/app/calendar-2/id415181149

According to the report of Arstechnica,

"On the one hand, using the user's CPU for cryptomining has become extremely unpopular," Thomas Reed, director of Mac offerings at anti-malware provider Malwarebytes, told Ars. "The fact that this is the default is something I don't like. I would want to see a legit app informing the user in advance or making it an option that can be turned on but is off by default. On the other hand, they [the developers] do disclose that they are doing it and give other options for people who don't like it. My personal feeling on this is that, given the disclosure, I think the user should be allowed to make their own choice. Some people might be perfectly willing to let an app like this mine cryptocurrency so that they can use it for free."



Qbix founder given statement to Arstechnica in email,
In an email, Qbix founder Gregory Magarshak said the rollout of the currency miner has been complicated by two bugs that prevented it from working as intended. The first flaw caused the miner to run indefinitely, even when users changed the default setting. The second bug caused the miner to consume more resources than planned. Developers programmed the miner to use 10 percent to 20 percent of a Mac's computing power, depending on whether the machine was plugged in. The new miner has been using much higher percentages.

After some time  Magarshak replied,

We have decided to REMOVE the miner in the app. The next version will remove the option to get free features via mining. This is for three reasons:

1) The company which provided us the miner library did not disclose its source code, and it would take too long for them to fix the root cause of the CPU issue.

2) The rollout had a perfect storm of bugs which made it seem like our company *wanted* to mine crypto-currency without people's permission, and that goes against our whole ethos and vision for Qbix.

3) My own personal feeling that Proof of Work has a dangerous set of incentives which can lead to electricity waste on a global scale we've never seen before. We don't want to get sucked into this set of incentives, and hopefully our decision to ultimately remove the miner will set some sort of precedent for other apps as well.

Ultimately, even though we technically could have remedied the situation and continued on benefiting from the pretty large income such a miner generates, we took the above as a sign that we should get out of the "mining business" before we get sucked into the Proof of Work morass of incentives.

You can check here for entire analysis of Calendar App.

ROP- A Tool To Help You Writing Binary Exploits

$
0
0
ROP- A Tool To Help You Writing Binary Exploits


ROP- A Tool To Help You Writing Binary Exploits


OPTIONS

rop-tool v2.4.1

Help you to make binary exploits.

Usage: 

rop-tool <cmd> [OPTIONS]

Commands :

   gadget        Search gadgets
   patch         Patch the binary
   info          Print info about binary
   heap          Display heap structure
   disassemble   Disassemble the binary
   search        Search on binary
   help          Print help
   version       Print version

Try "rop-tool help <cmd>" for more informations about a command.

GADGET COMMAND

Usage :rop-tool gadget [OPTIONS] [FILENAME]

OPTIONS:

  --arch, -A   Select an architecture (x86, x86-64, arm, arm64)
  --all, -a    Print all gadgets (even gadgets which are not uniq)
  --depth, -d  [d]  Specify the depth for gadget searching (default is 5)
  --flavor, -f [f]  Select a flavor (att or intel)
  --no-filter, -F   Do not apply some filters on gadgets
  --help, -h        Print this help message
  --no-color, -N    Do not colorize output

SEARCH COMMAND

Usage :rop-tool search [OPTIONS] [FILENAME]

OPTIONS:
  --all-string, -a  [n]  Search all printable strings of at least [n] caracteres. (default is 6)
  --byte, -b       [b]  Search the byte [b] in binary
  --dword, -d      [d]  Search the dword [d] in binary
  --help, -h       Print this help message
  --no-color, -N   Don't colorize output
  --qword, -q      [q]  Search the qword [q] in binary
  --raw, -r        Open file in raw mode (don't considere any file format)
  --split-string, -s  [s]  Search a string "splited" in memory (which is not contiguous in memory)
  --string, -S        [s]  Search a string (a byte sequence) in binary
  --word, -w          [w]  Search the word [w] in binary

PATCH COMMAND

Usage :rop-tool patch [OPTIONS] [FILENAME]

OPTIONS:
  --address, -a   [a]  Select an address to patch
  --bytes, -b    [b]  A byte sequence (e.g. : "\xaa\xbb\xcc") to write
  --filename, -f  [f]  Specify the filename
  --help, -h           Print this help message
  --offset, -o    [o]  Select an offset to patch (from start of the file)
  --output, -O    [o]  Write to an another filename
  --raw, -r            Open file in raw mode

INFO COMMAND

Usage :rop-tool info [OPTIONS] [FILENAME]

OPTIONS:
  --all, -a                 Show all infos
  --segments, -l           Show segments
  --sections, -s           Show sections
  --syms, -S               Show symbols
  --filename, -f      [f]  Specify the filename
  --help, -h               Print this help message
  --no-color, -N           Disable colors

HEAP COMMAND

Usage :rop-tool heap [OPTIONS] [COMMAND]

OPTIONS:
  --calloc, -C             Trace calloc calls
  --free, -F               Trace free calls
  --realloc, -R            Trace realloc calls
  --malloc, -M             Trace malloc calls
  --dumpdata, -d           Dump chunk's data
  --output, -O             Output in a file
  --help, -h               Print this help message
  --tmp, -t        <d>     Specify the writable directory, to dump the library (default: /tmp/)
  --no-color, -N           Do not colorize output

Small explication about output of heap command

Each line correspond to a malloc chunk, and the heap is dumped after each execution of heap functions (free, malloc, realloc, calloc)

  • addr: is the real address of the malloc chunk
  • usr_addr: is the address returned by malloc functions to user
  • size: is the size of the malloc chunk
  • flags: P is PREV_INUSE, M is IS_MAPED and A is NON_MAIN_ARENA


DISASSEMBLE COMMAND

Usage :rop-tool dis [OPTIONS] [FILENAME]

OPTIONS:
  --help, -h               Print this help message
  --no-color, -N           Do not colorize output
  --address, -a    <a>     Start disassembling at address <a>
  --offset, -o     <o>     Start disassembling at offset <o>
  --sym, -s        <s>     Disassemble symbol
  --len, -l        <l>     Disassemble only <l> bytes
  --arch, -A       <a>     Select architecture (x86, x86-64, arm, arm64)
  --flavor, -f     <f>     Change flavor (intel, att)

FEATURES


  • String searching, Gadget searching, patching, info, heap visualization, disassembling
  • Colored output
  • Intel and AT&T flavor
  • Support of ELF, PE and MACH-O binary format
  • Support of big and little endian
  • Support of x86, x86_64, ARM and ARM64 architecture


EXAMPLES

Basic gadget searching

  • rop-tool gadget ./program

Display all gadgets with AT&T syntax

  • rop-tool gadget ./program -f att -a

Search in RAW x86 file

  • rop-tool gadget ./program -A x86

Search a "splitted" string in the binary

  • rop-tool search ./program -s "/bin/sh"

Search all strings in binary

  • rop-tool search ./program -a

Patch binary at offset 0x1000, with "\xaa\xbb\xcc\xdd" and save as "patched" :

  • rop-tool patch ./program -o 0x1000 -b "\xaa\xbb\xcc\xdd" -O patched

Visualize heap allocation of /bin/ls command :

  • rop-tool heap /bin/ls

Disassemble 0x100 bytes at address 0x08048452

  • rop-tool dis /bin/ls -l 0x100 -a 0x08048452


Ubuntu Patches The Raspberry Pi 2 kernel Security Vulnerabilities

$
0
0
Ubuntu Patches The Raspberry Pi 2 kernel Security Vulnerabilities


Ubuntu 17.10 Patches The Raspberry Pi 2 Kernel Security Vulnerabilities


linux, linux-raspi2 vulnerabilities

A security issue affects these releases of Ubuntu and its derivatives:

Ubuntu 17.10: Several security issues were fixed in the Linux kernel.

Software Description
  • linux - Linux kernel
  • linux-raspi2 - Linux kernel for Raspberry Pi 2

Details

USNS 3541-1 and 3523-1 provided mitigations for Spectre and Meltdown (CVE-2017-5715, CVE-2017-5753, CVE-2017-5754) for the i386, amd64, and ppc64el architectures in Ubuntu 17.10. This update provides the corresponding mitigations for the arm64 architecture. Original advisory details:

Jann Horn discovered that microprocessors utilizing speculative execution and indirect branch prediction may allow unauthorized memory reads via sidechannel attacks. This flaw is known as Meltdown. A local attacker could use this to expose sensitive information, including kernel memory. (CVE-2017-5754) and  (CVE-2017-5715, CVE-2017-5753)

Update instructions

The problem can be corrected by updating your system to the following package versions:

Ubuntu 17.10
  • linux-image-4.13.0-1015-raspi2 - 4.13.0-1015.16
  • linux-image-4.13.0-37-generic - 4.13.0-37.42
  • linux-image-4.13.0-37-generic-lpae - 4.13.0-37.42
  • linux-image-4.13.0-37-lowlatency - 4.13.0-37.42
  • linux-image-generic - 4.13.0.37.40
  • linux-image-generic-lpae - 4.13.0.37.40
  • linux-image-lowlatency - 4.13.0.37.40
  • linux-image-raspi2 - 4.13.0.1015.13

Update:

Linux kernel for Raspberry Pi 2If the update-notifier-common package is installed, Ubuntu will alert you about pending updates via the message of the day (motd) upon console or remote login.

After logging in, you can check for and apply new updates with:

$ sudo apt-get update
$ sudo apt-get dist-upgrade

When performing an update, first review what apt is going to do, then confirm that you want to apply the updates (this is particularly true when running the development release).

If you would prefer to have updates applied automatically, make sure the unattended-upgrades package is installed, then run 'sudo dpkg-reconfigure unattended-upgrades'. Please note that updates may restart services on your server, so this may not be appropriate for all environments.

To update your system, please follow these instructions here.

After a standard system update you need to reboot your computer to make all the necessary changes.

ATTENTION: 

Due to an unavoidable ABI change the kernel updates have been given a new version number, which requires you to recompile and reinstall all third party kernel modules you might have installed. Unless you manually uninstalled the standard kernel metapackages (e.g. linux-generic, linux-generic-lts-RELEASE, linux-virtual, linux-powerpc), a standard system upgrade will automatically perform this as well.

Russian Hackers Cyber Attack on U.S.A Nuclear Energy Industry Sectors

$
0
0
Russian Hackers Cyber Attack on USA Energy and Nuclear Industry Sectors


Russian Hackers Cyber Attack on U.S.A  Nuclear Energy Industry Sectors


The Joint investigation of Department of Homeland Security (DHS) and Federal Bureau of Investigation (FBI). This alert information on Russian government action targeting U.S government entities as well as organizations in the energy, nuclear, commercial.

This is not the first time when Russia is attacking on US official computer systems. It was observed during U.S president election in 2016 too.

According to Forbes,
The electric grid is a system of systems, managed by thousands of people, computers and manual controls, with data supplied by tens of thousands of sensors connected by a wide variety of communications networks. Over the next 20 years, the growth in data flowing through our grid will far exceed the flow of electricity. So it is essential that we protect it from cyber-attack.

Nuclear plants are one of the best protected of all systems from possible cyber threats in America.

‘United States utilities with nuclear assets have very robust cyber security programs dating back to the days of Y2K,’ says David Blee, Executive Director of the National Nuclear Infrastructure Council. ‘Operational plant systems controls are segregated from normal business software by several layers of protection, including physical means.’

But the thing is Nuclear industry does not use firewalls to isolate these systems.

The Trump administration accused Moscow on Thursday of an elaborate plot to penetrate America’s electric grid, factories, water supply and air travel through hacking.

U.S. nuclear plants are designed as operational “islands” that are not connected to the internet and other networks. Nuclear power provides about 20 percent of the nation’s electricity.

According to report of US-CERT.
Domain Controllers, File and Email Servers were affected. DHS and FBI characterize the activity as a multi stage intrusion campaign by Russian government cyber actors who targeted small commercial facilities 'networks where they staged malware, conducted spear phsihing and gained remote access into energy sector networks. After obtaining access the Russian government cyber actors conducted network reconnaissance moved laterally and collected information pertaining to Industrial Control Systems (ICS).
   

Uitkyk: Android Frida Library To Hunt Android Malware

$
0
0
Uitkyk: Android Frida Library To Hunt Android Malware



Uitkyk: Android Frida Library To Hunt Android Malware


Uitkyk is a custom Android Frida libary which provides an API to analyze Android applications for malicious activity. This is a PoC library to illustrate the capabilities of performing runtime analysis on Android. Additionally Uitkyk is a collection of resources to assist in the identification of malicious Android applications at runtime.

This Repo

The folder "Frida Scripts" contains some basic Frida scripts to assist in the runtime analysis of Android applications. The folder "Android Library" contains the custom Android Frida library which can be used by Android applications to interact with Frida server instances. The folder "UitkykDemoApp" contains a demo Android application which utilizes the Uitkyk library.

Uitkyk Usage

To use the Uitkyk library, add the module to your Android application as a regular Android module. Currently there are two methods supported. To run the Frida equivelant of "frida-ps -U", use:

UitkykUtils uitkykUtils = new UitkykUtils(fridaHost, fridaPort);
uitkykUtils.analyzeProcess(this.pid);

To run the Frida equivelant of "frida -U -l AnalyzingHeapForObjects.js com.an.android.app", use:

UitkykUtils uitkykUtils= new UitkykUtils(fridaHost,fridaPort);
uitkykUtils.fridaPS();

Requirements

A Frida Server instance is required to be running on the device. The defaults will suffice but a custom host and IP can be used.

Scripts

The scripts located in the Scripts folder can be run as following:

frida -U -l AnalyzingHeapForObjects.js com.an.android.app
frida -U -l CatchingRuntimeExec.js com.an.android.app

Uitkyk Demo App

This application uses the Uitkyk library. Import the library into the app to ensure the application builds and runs. To ensure that the demo app runs, a local instance of Frida Server is required to be running locally on the device.

Download

Indian Army Warns, Chinese Hackers Targeting WhatsApp To Steal Information

$
0
0
Indian Army Warns Chinese Hackers Targeting WhatsApp To Steal Information


Indian Army Warns, Chinese Hackers Targeting WhatsApp To Steal Information


Chinese Hackers are trying to hack WhatsApp and steal your personal data.


Army advised users to be vigilant and urged them to conduct regular audits of their groups to see if any number starting with +86 had joined a group.

"The Chinese use all kinds of platforms to penetrate your digital world. WhatsApp groups are a new way of hacking into your system.

The Additional Directorate General of Public Interface (ADGPI) said the Chinese were penetrating the digital world.

Chinese numbers starting with +86 barge into your groups and start extracting all the data," says the video, tweeted from the army's official handle.

In case you change the SIM, destroy it completely,” the video said. It went to add that information mined from such groups was being leaked to Chinese hackers

"Stay cautious, stay alert, stay safe!


It is not the first time that China are using digital technique for information gathering. We have reported earlier Baidu Apps are Spying personal data and Leaked Information, Chinese Selfie App Is Spying On Your Smartphone.

NMap New Version 7.70 Released With Hundred of New OS And Service Fingerprints, 9 New NSE Scripts

$
0
0
NMap New Version 7.70 Released With Hundreds of New OS And Service Fingerprints

NMap New Version 7.70 Released With Hundred of New OS And Service Fingerprints


Nmap Free Security Scanner, Port Scanner, & Network Exploration Tool. Download open source software for Linux, Windows, UNIX, FreeBSD, etc.

It includes hundreds of new OS and service fingerprints, 9 new NSE scripts (for a total of 588), a much-improved version of our Npcap windows packet capturing library/driver, and service detection improvements to make -sV faster and more accurate. 

And those are just a few of the dozens of improvements described below.


Nmap 7.70 source code and binary packages for Linux, Windows, and Mac are available for free

If you find any bugs in this release, please let us know on the Nmap Dev list or bug tracker as described at https://nmap.org/book/man-bugs.html.

Here is the full list of significant changes in NMAP:


• [Windows] We made a ton of improvements to our Npcap Windows packet capturing library (https://nmap.org/npcap/) for greater performance and stability, as well as smoother installer and better 802.11 raw framecapturing support. Nmap 7.70 updates the bundled Npcap from version 0.93 to 0.99-r2, including all these changes from the last seven Npcap releases:

• Integrated all of your service/version detection fingerprints submitted from March 2017 to August 2017 (728 of them). The signature count went up 1.02% to 11,672, including 26 new softmatches.  We now detect 1224 protocols from filenet-pch, lscp, and netassistant to sharp-remote, urbackup, and watchguard.  We will try to integrate the remaining submissions in the next release.

• Integrated all of your IPv4 OS fingerprint submissions from September 2016 to August 2017 (667 of them). Added 298 fingerprints, bringing the new total to 5,652. Additions include iOS 11, macOS Sierra, Linux 4.14, Android 7, and more.

• Integrated all 33 of your IPv6 OS fingerprint submissions from September 2016 to August 2017. New groups for OpenBSD 6.0 and FreeBSD 11.0 were added, as well as strengthened groups for Linux and OS X.

• Added the --resolve-all option to resolve and scan all IP addresses of a host.  This essentially replaces the resolveall NSE script. [Daniel Miller]

• [NSE][SECURITY] Nmap developer nnposter found a security flaw (directory traversal vulnerability) in the way the non-default http-fetch script sanitized URLs. If a user manualy ran this NSE script against a malicious web server, the server could potentially (depending on NSE arguments used) cause files to be saved outside the intended destination directory. Existing files couldn't be overwritten.  We fixed http-fetch, audited our other scripts to ensure they didn't make this mistake, and updated the httpspider library API to protect against this by default. [nnposter, Daniel Miller]

• [NSE] Added 9 NSE scripts, from 8 authors, bringing the total up to 588! They are all listed at https://nmap.org/nsedoc/, and the summaries are below:

   - deluge-rpc-brute performs brute-force credential testing against
   Deluge BitTorrent RPC services, using the new zlib library. [Claudiu Perta]
   - hostmap-crtsh lists subdomains by querying Google's Certificate
   Transparency logs. [Paulino Calderon]
   - [GH#892] http-bigip-cookie decodes unencrypted F5 BIG-IP cookies and
   reports back the IP address and port of the actual server behind the
   load-balancer. [Seth Jackson]
   - http-jsonp-detection Attempts to discover JSONP endpoints in web
   servers. JSONP endpoints can be used to bypass Same-origin Policy
   restrictions in web browsers. [Vinamra Bhatia]
   - http-trane-info obtains information from Trane Tracer SC controllers
   and connected HVAC devices. [Pedro Joaquin]
   - [GH#609] nbd-info uses the new nbd.lua library to query Network Block
   Devices for protocol and file export information. [Mak Kolybabi]
   - rsa-vuln-roca checks for RSA keys generated by Infineon TPMs
   vulnerable to Return Of Coppersmith Attack (ROCA) (CVE-2017-15361). Checks
   SSH and TLS services. [Daniel Miller]
   - [GH#987] smb-enum-services retrieves the list of services running on a
   remote Windows machine. Modern Windows systems requires a privileged domain
   account in order to list the services. [Rewanth Cool]
   - tls-alpn checks TLS servers for Application Layer Protocol Negotiation
   (ALPN) support and reports supported protocols. ALPN largely replaces NPN,
   which tls-nextprotoneg was written for. [Daniel Miller]

• [GH#978] Fixed Nsock on Windows giving errors when selecting on STDIN.
This was causing Ncat 7.60 in connect mode to quit with error: libnsock select_loop(): nsock_loop error 10038: An operation was attempted on something that is not a socket.  [nnposter]

• [Ncat][GH#197][GH#1049] Fix --ssl connections from dropping on renegotiation, the same issue that was partially fixed for server mode in [GH#773]. Reported on Windows with -e by pkreuzt and vinod272. [Daniel
Miller]

• [NSE][GH#1062][GH#1149] Some changes to brute.lua to better handle misbehaving or rate-limiting services. Most significantly, brute.killstagnated now defaults to true. Thanks to xp3s and Adamtimtim for reporing infinite loops and proposing changes.

• [NSE] VNC scripts now support Apple Remote Desktop authentication (auth type 30) [Daniel Miller]

• [NSE][GH#1111] Fix a script crash in ftp.lua when PASV connection timed out. [Aniket Pandey]

• [NSE][GH#1114] Update bitcoin-getaddr to receive more than one response message, since the first message usually only has one address in it. [h43z]

• [Ncat][GH#1139] Ncat now selects the correct default port for a given proxy type. [Pavel Zhukov]

• [NSE] memcached-info can now gather information from the UDP memcached service in addition to the TCP service. The UDP service is frequently used as a DDoS reflector and amplifier. [Daniel Miller]

• [NSE][GH#1129] Changed url.absolute() behavior with respect to dot and dot-dot path segments to comply with RFC 3986, section 5.2. [nnposter]

• Removed deprecated and undocumented aliases for several long options that used underscores instead of hyphens, such as --max_retries. [Daniel Miller]

• Improved service scan's treatment of soft matches in two ways. First of all, any probes that could result in a full match with the soft matched service will now be sent, regardless of rarity. This improves the chances of matching unusual services on non-standard ports.  Second, probes are now skipped if they don't contain any signatures for the soft matched service.

Perviously the probes would still be run as long as the target port number matched the probe's specification.  Together, these changes should make service/version detection faster and more accurate.  For more details on how it works, see https://nmap.org/book/vscan.html. [Daniel Miller]

• --version-all now turns off the soft match optimization, ensuring that all probes really are sent, even if there aren't any existing match lines for the softmatched service. This is slower, but gives the most comprehensive results and produces better fingerprints for submission.
[Daniel Miller]

• [NSE][GH#1083] New set of Telnet softmatches for version detection based on Telnet DO/DON'T options offered, covering a wide variety of devices and operating systems. [D Roberson]

• [GH#1112] Resolved crash opportunities caused by unexpected libpcap version string format. [Gisle Vanem, nnposter]

• [NSE][GH#1090] Fix false positives in rexec-brute by checking responses for indications of login failure. [Daniel Miller]

• [NSE][GH#1099] Fix http-fetch to keep downloaded files in separate destination directories. [Aniket Pandey]

• [NSE] Added new fingerprints to http-default-accounts:
+ Hikvision DS-XXX Network Camera and NUOO DVR [Paulino Calderon]
+ [GH#1074] ActiveMQ, Purestorage, and Axis Network Cameras [Rob
Fitzpatrick, Paulino Calderon]

• Added a new service detection match for WatchGuard Authentication Gateway. [Paulino Calderon]

• [NSE][GH#1038][GH#1037] Script qscan was not observing interpacket delays
(parameter qscan.delay). [nnposter]

• [NSE][GH#1046] Script http-headers now fails properly if the target does not return a valid HTTP response. [spacewander]

• [Ncat][Nsock][GH#972] Remove RC4 from the list of TLS ciphers used by default, in accordance with RFC 7465. [Codarren Velvindron]

• [NSE][GH#1022] Fix a false positive condition in ipmi-cipher-zero caused by not checking the error code in responses. Implementations which return
an error are not vulnerable. [Juho Jokelainen]

• [NSE][GH#958] Two new libraries for NSE.
   - idna - Support for internationalized domain names in applications
   (IDNA)
   - punycode (a transfer encoding syntax used in IDNA) [Rewanth Cool]

• [NSE] New fingerprints for http-enum:
   - [GH#954] Telerik UI CVE-2017-9248 [Harrison Neal]
   - [GH#767] Many WordPress version detections [Rewanth Cool]

• [GH#981][GH#984][GH#996][GH#975] Fixed Ncat proxy authentication issues [nnposter]:

   - Usernames and/or passwords could not be empty
   - Passwords could not contain colons
   - SOCKS5 authentication was not properly documented
   - SOCKS5 authentication had a memory leak

• [GH#1009][GH#1013] Fixes to autoconf header files to allow autoreconf to be run. [Lukas Schwaighofer]

• [GH#977] Improved DNS service version detection coverage and consistency by using data from a Project Sonar Internet wide survey. Numerouse false positives were removed and reliable softmatches added. Match lines for version.bind responses were also conslidated using the technique below.
[Tom Sellers]

• [GH#977] Changed version probe fallbacks so as to work cross protocol (TCP/UDP). This enables consolidating match lines for services where the responses on TCP and UDP are similar. [Tom Sellers]

• [NSE][GH#532] Added the zlib library for NSE so scripts can easily handle compression. This work started during GSOC 2014, so we're particularly pleased to finally integrate it! [Claudiu Perta, Daniel Miller]

• [NSE][GH#1004] Fixed handling of brute.retries variable. It was being treated as the number of tries, not retries, and a value of 0 would result in infinite retries. Instead, it is now the number of retries, defaulting to 2 (3 total tries), with no option for infinite retries.

• [NSE] http-devframework-fingerprints.lua supports Jenkins server detection and returns extra information when Jenkins is detected [Vinamra Bhatia]

• [GH#926] The rarity level of MS SQL's service detection probe was decreased. Now we can find MS SQL in odd ports without increasing version intensity. [Paulino Calderon]

• [GH#957] Fix reporting of zlib and libssh2 versions in "nmap --version". We were always reporting the version number of the included source, even when a different version was actually linked. [Pavel Zhukov]

• Add a new helper function for nmap-service-probes match lines: $I(1,">") will unpack an unsigned big-endian integer value up to 8 bytes wide from capture 1. The second option can be "<" for little-endian. [Daniel Miller]

Enjoy this new release and please do let us know if you find any problems!

Facebook CEO Mark Zuckerberg Admits It is "Breach of Trust" on Cambridge Analytica Scandal

$
0
0
Facebook CEO Mark Zuckerberg Admits It is "Breach of Trust" on Cambridge Analytica Scandal


Facebook CEO Mark Zuckerberg Admits It is "Breach of Trust" on Cambridge Analytica Scandal.


Biggest social media platform Facebook involving Cambridge Analytica breach. Currently, Facebook has 2 Billion active users monthly.


Who is Cambridge Analytica (CA)?

Cambridge Analytica is a privately held company that combines data mining, data brokerage, and data analysis with strategic communication for the electoral process. It was founded in 2013.

In 2015, it became known as the data analysis company working initially for Ted Cruz's presidential campaign. In 2016 CA worked for Donald Trump's presidential campaign, and on the Leave. EU-campaign for the United Kingdom's withdrawal from the European Union.

What is Cambridge Analytica Data Scandal?

On 17 March 2018, The New York Times and The Observer reported on Cambridge Analytica's use of personal information acquired from Facebook, without users' permission, by an external researcher who claimed to be collecting it for academic purposes. In response, Facebook banned Cambridge Analytica from advertising on its platform.

The Guardian further reported that Facebook had known about this security breach for two years but had done nothing to protect its users.

Mark Zuckerberg talked about it in his Facebook post,

"I want to share an update on the Cambridge Analytica situation -- including the steps we've already taken and our next steps to address this important issue.

We have a responsibility to protect your data, and if we can't then we don't deserve to serve you. I've been working to understand exactly what happened and how to make sure this doesn't happen again. The good news is that the most important actions to prevent this from happening again today we have already taken years ago. But we also made mistakes, there's more to do, and we need to step up and do it.

Here's a timeline of the events:

In 2007, we launched the Facebook Platform with the vision that more apps should be social. Your calendar should be able to show your friends' birthdays, your maps should show where your friends live, and your address book should show their pictures. To do this, we enabled people to log into apps and share who their friends were and some information about them.

In 2013, a Cambridge University researcher named Aleksandr Kogan created a personality quiz app. It was installed by around 300,000 people who shared their data as well as some of their friends' data. Given the way our platform worked at the time this meant Kogan was able to access tens of millions of their friends' data.

In 2014, to prevent abusive apps, we announced that we were changing the entire platform to dramatically limit the data apps could access. Most importantly, apps like Kogan's could no longer ask for data about a person's friends unless their friends had also authorized the app. We also required developers to get approval from us before they could request any sensitive data from people. These actions would prevent any app like Kogan's from being able to access so much data today.

In 2015, we learned from journalists at The Guardian that Kogan had shared data from his app with Cambridge Analytica. It is against our policies for developers to share data without people's consent, so we immediately banned Kogan's app from our platform, and demanded that Kogan and Cambridge Analytica formally certify that they had deleted all improperly acquired data. They provided these certifications.

Last week, we learned from The Guardian, The New York Times and Channel 4 that Cambridge Analytica may not have deleted the data as they had certified. We immediately banned them from using any of our services. Cambridge Analytica claims they have already deleted the data and has agreed to a forensic audit by a firm we hired to confirm this. We're also working with regulators as they investigate what happened.

This was a breach of trust between Kogan, Cambridge Analytica and Facebook. But it was also a breach of trust between Facebook and the people who share their data with us and expect us to protect it. We need to fix that.

In this case, we already took the most important steps a few years ago in 2014 to prevent bad actors from accessing people's information in this way. But there's more we need to do and I'll outline those steps here:

First, we will investigate all apps that had access to large amounts of information before we changed our platform to dramatically reduce data access in 2014, and we will conduct a full audit of any app with suspicious activity. We will ban any developer from our platform that does not agree to a thorough audit. And if we find developers that misused personally identifiable information, we will ban them and tell everyone affected by those apps. That includes people whose data Kogan misused here as well.

Second, we will restrict developers' data access even further to prevent other kinds of abuse. For example, we will remove developers' access to your data if you haven't used their app in 3 months. We will reduce the data you give an app when you sign in -- to only your name, profile photo, and email address. We'll require developers to not only get approval but also sign a contract in order to ask anyone for access to their posts or other private data. And we'll have more changes to share in the next few days.

Third, we want to make sure you understand which apps you've allowed to access your data. In the next month, we will show everyone a tool at the top of your News Feed with the apps you've used and an easy way to revoke those apps' permissions to your data. We already have a tool to do this in your privacy settings, and now we will put this tool at the top of your News Feed to make sure everyone sees it.

Beyond the steps we had already taken in 2014, I believe these are the next steps we must take to continue to secure our platform.

I started Facebook, and at the end of the day I'm responsible for what happens on our platform. I'm serious about doing what it takes to protect our community. While this specific issue involving Cambridge Analytica should no longer happen with new apps today, that doesn't change what happened in the past. We will learn from this experience to secure our platform further and make our community safer for everyone going forward.

I want to thank all of you who continue to believe in our mission and work to build this community together. I know it takes longer to fix all these issues than we'd like, but I promise you we'll work through this and build a better service over the long term."


Zuckerberg given interview to CNN,

Security isn't a problem that you ever fully solve," Zuckerberg told Segall on Wednesday night. "We're going to be working on this forever, as long as this community remains an important thing in the world."

INDIA shuts down the local website of Cambridge Analytica.

Ravi Shankaar prasad , Information Technology Minister of India has said in Twitter @rsprasad,
We welcome the fact that facebook has one of the highest number of users from India but if any theft of data of Indians takes place in collusion with other companies for manipulation of democratic processes then that will not be tolerated. 

Facebook shares going down, after the Mark has been confirmed data breach.

Netflix Announces Its First Public Bug Bounty Program

$
0
0
Netflix Announces Its First Public Bug Bounty Program

Netflix Announces its First Public Bug Bounty Program. 


Now Cyber Security researchers report the vulnerability to NetFlix in Bug Crowd Platform to keep it secure and safe.


Bug Bounty Program criteria between $100 – $15,000 as per vulnerability.

Netflix is an American entertainment company founded by Reed Hastings and Marc Randolph on August 29, 1997, in Scotts Valley, California. It specializes in and provides streaming media, video-on-demand online, and, DVD by mail. In 2013, Netflix expanded into film and television production as well as online distribution.

Netflix require that all researchers:


  • Do not access customer or employee personal information, pre-release Netflix content, or Netflix confidential information. If you accidentally access any of these, please stop testing and submit the vulnerability.
  • Stop testing and report the issue immediately if you gain access to any non-public application or non-public credentials.
  • Do not degrade the Netflix user experience, disrupting production systems, or destroy data during security testing.
  • Perform research only within the scope set out below.
  • Use the Bugcrowd report submission form to report vulnerability information to us.
  • Collect only the information necessary to demonstrate the vulnerability.
  • Submit any necessary screenshots, screen captures, network requests, reproduction steps or similar using the Bugcrowd submission form (do not use third party file sharing sites).
  • When investigating a vulnerability, please only target your own account and do not attempt to access data from anyone else’s account.
  • Follow the Bugcrowd “Coordinated Disclosure” rules.


If you fulfill these requirements, Netflix will:


  • Work with you to understand and attempt to resolve the issue quickly (confirming the report within 7 days of submission);
  • Recognize your contribution to our Security Researcher Hall of Fame, if you are the first to report the issue and we make a code or configuration change based on the issue.
  • Pay you for your research for unique vulnerabilities that meet the guidelines listed below if you are the first to report the issue to us using the Bugcrowd portal.
  • To encourage responsible disclosure, Netflix will not bring a lawsuit against you or ask law enforcement to investigate you if we determine that your research and disclosure meets these requirements and guidelines. 


Focus Areas

We encourage researchers to focus their efforts in the following areas:

  • Cross Site Scripting (XSS)
  • Cross-Site Request Forgery (CSRF)
  • SQL Injection (SQLi)
  • Authentication related issues
  • Authorization related issues
  • Data Exposure
  • Redirection attacks
  • Remote Code Execution
  • Business Logic
  • MSL Protocol (https://github.com/Netflix/msl)
  • Particularly clever vulnerabilities or unique issues that do not fall into explicit categories
  • Mobile-specific API vulnerabilities


Check here for more details.
Viewing all 855 articles
Browse latest View live