Hacking Articles Tips Tricks Videos Tutorials
Photo
Black Hat Ethical Hacking
Vulnerability Disclosure Policy
BHEH’s Vulnerability Disclosure PolicyBlack Hat Ethical Hacking Vulnerability Disclosure PolicyIntroduction
At Black Hat Ethical Hacking (BHEH), we understand the importance of maintaining the security and privacy of our technology and users. Our goal is to ensure that all systems and data are protected from unauthorized access and tampering. As part of this effort, we encourage responsible vulnerability research and disclosure. This policy outlines our definition of good faith in the context of finding and reporting vulnerabilities, as well as what researchers can expect from us in return.
Expectations
For researchers working in accordance with this policy, BHEH promises to:
* Offer Safe Harbor protection as defined by this policy for your vulnerability research related to this policy.
* Provide a prompt and timely initial response to your report submission.
* Work with you to understand and validate your report.
* Take appropriate action to remediate discovered vulnerabilities in a timely manner.
* Recognize your contribution to improving our security if you are the first to report a unique vulnerability and your report triggers a code or configuration change.
Please note that BHEH does not offer compensation for vulnerability information, but will credit you should we deem it to be a solid impact.
Rules of Engagement
To encourage vulnerability research and to avoid any confusion between good-faith hacking and malicious attacks, researchers must abide by the following rules:
* Do not exploit the issue or issue a denial of service attack.
* Do not change or alter the configuration or data of our systems.
* Do not engage in any activities that violate any applicable laws or regulations.
* Do not use social engineering techniques or attempt to access or destroy data.
* Do not publicly disclose the issue before BHEH has confirmed it and provided a remedy.
Safe Harbor Definition
Researchers are authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws) and BHEH will not initiate or support legal action against you for accidental, good-faith violations of this policy when conducting genuine vulnerability research in accordance with this policy. Researchers are exempt from the Digital Millennium Copyright Act (DMCA) and BHEH will not bring a claim against you for circumvention of technology controls when conducting genuine vulnerability research in accordance with this policy. Researchers are exempt from restrictions in our Terms and Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy. Researchers must conduct their work in a lawful, helpful, and good-faith manner.
Reporting
To report a security issue or vulnerability, researchers must follow this process:
* Aggregate as much technical information as possible, including steps to reproduce and validate the issue.
* Encrypt your report using BHEH’s GPG key.
* Within 24 hours of discovery, email your encrypted report to the BHEH security team via offensivesecurity@blackhatethicalhacking.com.
* Allow up to 10 business days for confirmation of the reported issue.
Our Commitment
BHEH is committed to securing the confidentiality, integrity, and availability of our systems and the data they store. We take the security of our technology and users seriously and appreciate your contribution to our security efforts. We will work with you to promptly address and remedy any vulnerabilities discovered.
If you have any questions or concerns regarding this policy, please do not hesitate to reach out to us at offensivesecurity@blackhatethicalhacking.com.
Effective Date: 7th of September, 2018
Revised Date: 5h or February 2023
If you have any questions about these Terms, please contact us.
The post Vulnerability Disclosure Policy first appeared on Black Hat Ethical Hacking.
Vulnerability Disclosure Policy
BHEH’s Vulnerability Disclosure PolicyBlack Hat Ethical Hacking Vulnerability Disclosure PolicyIntroduction
At Black Hat Ethical Hacking (BHEH), we understand the importance of maintaining the security and privacy of our technology and users. Our goal is to ensure that all systems and data are protected from unauthorized access and tampering. As part of this effort, we encourage responsible vulnerability research and disclosure. This policy outlines our definition of good faith in the context of finding and reporting vulnerabilities, as well as what researchers can expect from us in return.
Expectations
For researchers working in accordance with this policy, BHEH promises to:
* Offer Safe Harbor protection as defined by this policy for your vulnerability research related to this policy.
* Provide a prompt and timely initial response to your report submission.
* Work with you to understand and validate your report.
* Take appropriate action to remediate discovered vulnerabilities in a timely manner.
* Recognize your contribution to improving our security if you are the first to report a unique vulnerability and your report triggers a code or configuration change.
Please note that BHEH does not offer compensation for vulnerability information, but will credit you should we deem it to be a solid impact.
Rules of Engagement
To encourage vulnerability research and to avoid any confusion between good-faith hacking and malicious attacks, researchers must abide by the following rules:
* Do not exploit the issue or issue a denial of service attack.
* Do not change or alter the configuration or data of our systems.
* Do not engage in any activities that violate any applicable laws or regulations.
* Do not use social engineering techniques or attempt to access or destroy data.
* Do not publicly disclose the issue before BHEH has confirmed it and provided a remedy.
Safe Harbor Definition
Researchers are authorized in accordance with the Computer Fraud and Abuse Act (CFAA) (and/or similar state laws) and BHEH will not initiate or support legal action against you for accidental, good-faith violations of this policy when conducting genuine vulnerability research in accordance with this policy. Researchers are exempt from the Digital Millennium Copyright Act (DMCA) and BHEH will not bring a claim against you for circumvention of technology controls when conducting genuine vulnerability research in accordance with this policy. Researchers are exempt from restrictions in our Terms and Conditions that would interfere with conducting security research, and we waive those restrictions on a limited basis for work done under this policy. Researchers must conduct their work in a lawful, helpful, and good-faith manner.
Reporting
To report a security issue or vulnerability, researchers must follow this process:
* Aggregate as much technical information as possible, including steps to reproduce and validate the issue.
* Encrypt your report using BHEH’s GPG key.
* Within 24 hours of discovery, email your encrypted report to the BHEH security team via offensivesecurity@blackhatethicalhacking.com.
* Allow up to 10 business days for confirmation of the reported issue.
Our Commitment
BHEH is committed to securing the confidentiality, integrity, and availability of our systems and the data they store. We take the security of our technology and users seriously and appreciate your contribution to our security efforts. We will work with you to promptly address and remedy any vulnerabilities discovered.
If you have any questions or concerns regarding this policy, please do not hesitate to reach out to us at offensivesecurity@blackhatethicalhacking.com.
Effective Date: 7th of September, 2018
Revised Date: 5h or February 2023
If you have any questions about these Terms, please contact us.
The post Vulnerability Disclosure Policy first appeared on Black Hat Ethical Hacking.
Hacking Articles Tips Tricks Videos Tutorials
Black Hat Ethical Hacking Exploit Code Released for Actively Exploited GoAnywhere MFT Vulnerability Exploit Code Released for Actively Exploited GoAnywhere MFT VulnerabilityPost Views: 1 Premium Contenthttps://www.blackhatethicalhacking.com/wp-content/up…
2/Images-for-the-News-posts-4-300x150.png Sh1mmer: A New Exploit Enables Unenrollment of Enterprise-Managed ChromebooksFebruary 1, 2023
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 Exploit Code Released for Actively Exploited GoAnywhere MFT Vulnerability first appeared on Black Hat Ethical Hacking.
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 Exploit Code Released for Actively Exploited GoAnywhere MFT Vulnerability first appeared on Black Hat Ethical Hacking.
“Securing Your API: A Guide to Protecting Against Common Vulnerabilities”
https://medium.com/@Theshahid/securing-your-api-a-guide-to-protecting-against-common-vulnerabilities-cb00513d76f0?source=rss------bug_bounty-5
https://medium.com/@Theshahid/securing-your-api-a-guide-to-protecting-against-common-vulnerabilities-cb00513d76f0?source=rss------bug_bounty-5
API (Application Programming Interface) vulnerability refers to weaknesses or flaws in a software application’s API that could be…Continue reading on Medium » (https://medium.com/@Theshahid/securing-your-api-a-guide-to-protecting-against-common-vulnerabilities-cb00513d76f0?source=rss------bug_bounty-5)
NULL Pointer Dereference [CWE-476]
https://medium.com/@ramawijayas.techdr7/null-pointer-dereference-cwe-476-8acc5f525b0d?source=rss------bug_bounty-5
https://medium.com/@ramawijayas.techdr7/null-pointer-dereference-cwe-476-8acc5f525b0d?source=rss------bug_bounty-5
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -Continue reading on Medium » (https://medium.com/@ramawijayas.techdr7/null-pointer-dereference-cwe-476-8acc5f525b0d?source=rss------bug_bounty-5)
How I Got +1000$ by Clickacking
https://medium.com/@mydudehello91/how-i-got-1000-by-clickacking-233e89d76ffd?source=rss------bug_bounty-5
https://medium.com/@mydudehello91/how-i-got-1000-by-clickacking-233e89d76ffd?source=rss------bug_bounty-5
As-Salaam-Alaikum (Peace be unto you) Hello Amazing hackers My name is Aryan I am a Bug Bounty Hunter. This is my Third Write-up, hope You…Continue reading on Medium » (https://medium.com/@mydudehello91/how-i-got-1000-by-clickacking-233e89d76ffd?source=rss------bug_bounty-5)
How I Got +1000$ by Clickjacking
As-Salaam-Alaikum (Peace be unto you) Hello Amazing hackers My name is Aryan I am a Bug Bounty Hunter. This is my Third Write-up, hope You…Continue reading on Medium »
Read more...
As-Salaam-Alaikum (Peace be unto you) Hello Amazing hackers My name is Aryan I am a Bug Bounty Hunter. This is my Third Write-up, hope You…Continue reading on Medium »
Read more...
NULL Pointer Dereference [CWE-476]
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -Continue reading on Medium »
Read more...
— — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — — -Continue reading on Medium »
Read more...
Hacking Articles Tips Tricks Videos Tutorials
Photo
hacking: security in practice
How to find the owner of a website
What websites/tools do you use to find the owner (or contact details) of a website/domain?
Thanks
submitted by /u/thesellercvf
[link] [comments]
How to find the owner of a website
What websites/tools do you use to find the owner (or contact details) of a website/domain?
Thanks
submitted by /u/thesellercvf
[link] [comments]
Hacking Articles Tips Tricks Videos Tutorials
Photo
hacking: security in practice
How to recover my gmail(it got disabled)
So long story short my main gmail was disabled by google. Like would be fine it it wasn’t linked to literally almost all my accounts since 2013 so now I can’t login in to many site and. Have lost years and years of personal pictures. I asked google to appeal however they refused is there some way to get access to my account still as I have several art classes and course that weren’t a few $100 save to my drive and Dropbox linked to that email.
submitted by /u/tilovespandas
[link] [comments]
How to recover my gmail(it got disabled)
So long story short my main gmail was disabled by google. Like would be fine it it wasn’t linked to literally almost all my accounts since 2013 so now I can’t login in to many site and. Have lost years and years of personal pictures. I asked google to appeal however they refused is there some way to get access to my account still as I have several art classes and course that weren’t a few $100 save to my drive and Dropbox linked to that email.
submitted by /u/tilovespandas
[link] [comments]
Best way to set up for assumed breach?
https://www.reddit.com/r/redteamsec/comments/10vyrcx/best_way_to_set_up_for_assumed_breach/
<!-- SC_OFF -->I have OSCP training and web app pentesting experience but I'm new to the red team/purple team type stuff. How do you folks normally set up for assumed breach scenarios? Say you have a client that wants to do an assumed breach purple team assessment of their on-prem domain and you have a cobalt strike server set up. How do you ask them to set up for you? Do you... ask them to set up a machine on the domain and give you creds to it? ask them to turn off whatever protections so you can put a beacon on the machine? just ask for information to vpn to the network? etc. What exactly is the normal way you would do this? <!-- SC_ON --> submitted by /u/Jumpy_Hamster (https://www.reddit.com/user/Jumpy_Hamster)
[link] (https://www.reddit.com/r/redteamsec/comments/10vyrcx/best_way_to_set_up_for_assumed_breach/) [comments] (https://www.reddit.com/r/redteamsec/comments/10vyrcx/best_way_to_set_up_for_assumed_breach/)
https://www.reddit.com/r/redteamsec/comments/10vyrcx/best_way_to_set_up_for_assumed_breach/
<!-- SC_OFF -->I have OSCP training and web app pentesting experience but I'm new to the red team/purple team type stuff. How do you folks normally set up for assumed breach scenarios? Say you have a client that wants to do an assumed breach purple team assessment of their on-prem domain and you have a cobalt strike server set up. How do you ask them to set up for you? Do you... ask them to set up a machine on the domain and give you creds to it? ask them to turn off whatever protections so you can put a beacon on the machine? just ask for information to vpn to the network? etc. What exactly is the normal way you would do this? <!-- SC_ON --> submitted by /u/Jumpy_Hamster (https://www.reddit.com/user/Jumpy_Hamster)
[link] (https://www.reddit.com/r/redteamsec/comments/10vyrcx/best_way_to_set_up_for_assumed_breach/) [comments] (https://www.reddit.com/r/redteamsec/comments/10vyrcx/best_way_to_set_up_for_assumed_breach/)
Spoofing MS Office comments
https://www.reddit.com/r/redteamsec/comments/10vz1zh/spoofing_ms_office_comments/
<!-- SC_OFF -->https://badoption.eu/blog/2023/02/06/spoof_office_comments.html MS Office does not verify comments, as they are stored in the file. Allows spoofing of author and or comments, even crosstenant for AAD. <!-- SC_ON --> submitted by /u/PfiatDe (https://www.reddit.com/user/PfiatDe)
[link] (https://www.reddit.com/r/redteamsec/comments/10vz1zh/spoofing_ms_office_comments/) [comments] (https://www.reddit.com/r/redteamsec/comments/10vz1zh/spoofing_ms_office_comments/)
https://www.reddit.com/r/redteamsec/comments/10vz1zh/spoofing_ms_office_comments/
<!-- SC_OFF -->https://badoption.eu/blog/2023/02/06/spoof_office_comments.html MS Office does not verify comments, as they are stored in the file. Allows spoofing of author and or comments, even crosstenant for AAD. <!-- SC_ON --> submitted by /u/PfiatDe (https://www.reddit.com/user/PfiatDe)
[link] (https://www.reddit.com/r/redteamsec/comments/10vz1zh/spoofing_ms_office_comments/) [comments] (https://www.reddit.com/r/redteamsec/comments/10vz1zh/spoofing_ms_office_comments/)
Let’s Go (VS) Code - Red Team style
https://www.reddit.com/r/redteamsec/comments/10vz40w/lets_go_vs_code_red_team_style/
<!-- SC_OFF -->https://badoption.eu/docs/blog/2023/01/31/code_c2.html VSCode has a protable binary, which also allows a reverse shell and some other nice features (File Explorer, Debugging, Local Port Forwarding). Authentication is via Github and hosting iscomplete on MS domains. PS: I am the author, so if there are any questions, or feedback let me know. <!-- SC_ON --> submitted by /u/PfiatDe (https://www.reddit.com/user/PfiatDe)
[link] (https://www.reddit.com/r/redteamsec/comments/10vz40w/lets_go_vs_code_red_team_style/) [comments] (https://www.reddit.com/r/redteamsec/comments/10vz40w/lets_go_vs_code_red_team_style/)
https://www.reddit.com/r/redteamsec/comments/10vz40w/lets_go_vs_code_red_team_style/
<!-- SC_OFF -->https://badoption.eu/docs/blog/2023/01/31/code_c2.html VSCode has a protable binary, which also allows a reverse shell and some other nice features (File Explorer, Debugging, Local Port Forwarding). Authentication is via Github and hosting iscomplete on MS domains. PS: I am the author, so if there are any questions, or feedback let me know. <!-- SC_ON --> submitted by /u/PfiatDe (https://www.reddit.com/user/PfiatDe)
[link] (https://www.reddit.com/r/redteamsec/comments/10vz40w/lets_go_vs_code_red_team_style/) [comments] (https://www.reddit.com/r/redteamsec/comments/10vz40w/lets_go_vs_code_red_team_style/)