SQL Joins

By -
Below is the nice little explanation of SQL joins, do read it and share it with your friends.


Comments

Post a Comment

Popular posts from this blog

Fixing Frida Server “TypeError: t is not a function” on Android

By -
Image
 Hi All, Recently I have faced an issue with running the frida on Android.  When using Frida for Android reverse engineering or runtime instrumentation, you might encounter this frustrating error immediately after starting the Frida server binary:      # /data/local/tmp/frida & And then suddenly:     {"type":"error","description":"TypeError: t is not a function"}     ...     {"type":"error","description":"TypeError: Cannot read properties of undefined (reading 'find')"} Root Cause: Google ART Runtime Module Android devices using com.google.android.art (a system module version of ART) can conflict with how Frida’s agent initializes. The module interferes with native libart.so loading, class resolution, or reflection APIs, which Frida relies on to set up its Java bridge. Even before you attach to an app, Frida attempts to bootstrap into the ART layer — this is where the failure happens. Fix ...
Read more

Ericsson BSCS iX R18 Billing & Rating (ADMX, MX) - Stored XSS (CVE-2020-29144, CVE-2020-29145)

By -
Image
Dear Reader, I was able to identify stored XSS in multiple web base modules of Ericsson BSCS iX R18 Billing & Rating platform  Below are its details: # Software description: Ericsson Billing is a convergent billing solution for telecoms that combines an unrivaled combination of out-of-the box features and high configurability. As an evolution of the widely-installed Ericsson BSCS iX, Ericsson Billing provides a low-risk but effective route to capture and secure revenue streams and take advantage of business opportunities from both traditional telecom services as well as digital services, 5G and IoT. # Technical Details & Impact: There are multiple web base modules in BSCS iX e.g. ADMX, MX (monitoring center), CX etc. It was observed that ADMX and MX are vulnerable to stored XSS, In most test cases session hijacking was also possible by utilizing the XSS vulnerability. This potentially allows for full account takeover, or exploiting admin's browsers using beef...
Read more

Bypassing BurpSuite "Failed to connect to website:port" issue

By -
Image
Hi readers, When performing penetration testing, it’s common to run into situations where an application or web portal works perfectly in a browser, but refuses to load once you route traffic through your interception proxy(e.g. Burp suite). Instead of the expected traffic flow, you might be greeted with errors such as: Error Failed to Connect to <website:port> This happens because some applications and servers enforce stricter connection requirements, such as enforcing TLS versions, specific cipher suites, or HTTP/2 negotiation. which the proxy cannot always handle correctly on its own. The Solution: Proxy Chaining (Upstream Proxy):  The workaround is to introduce an additional proxy layer that sits between your BurpSuite and the destination server . Your interception proxy connects to this new proxy, which then handles the final connection to the target. This approach is commonly called proxy chaining or upstream proxying . It ensures that your interception tool can still ...
Read more