Waraxe IT Security Portal
Login or Register
November 19, 2026
Menu
Home
Logout
Discussions
Forums
Members List
IRC chat
Tools
Base64 coder
MD5 hash
CRC32 checksum
ROT13 coder
SHA-1 hash
URL-decoder
Sql Char Encoder
Affiliates
y3dips ITsec
Md5 Cracker
User Manuals
AlbumNow
Content
Content
Sections
FAQ
Top
Info
Feedback
Recommend Us
Search
Journal
Your Account
User Info
Welcome, Anonymous
Nickname
Password
(Register)

Membership:
Latest: MichaelSnaRe
New Today: 0
New Yesterday: 0
Overall: 9144

People Online:
Visitors: 492
Members: 0
Total: 492
Full disclosure
Fastly Next-Gen WAF (Signal Sciences) agent fails open before rules load in Kubernetes sidecar deployments (vendor disputes; CVE pending)
[Tool] starshield-forensics v0.3.7: Offline Chromium LevelDB .log carver (Python stdlib, MIT)
Dropbear: the restriction names an address — permitopen/permitlisten not enforced for unix-socket forwarding, docker.sock reachable (HEAD 99baf182, live-proven)
Nightscout < 15.0.8: Stored XSS via WebSocket Treatment Writes (GHSA-5mrq-gpqw-q5v5)
SAPBleed: Pre-Auth Memory Disclosure and RCE in SAP NetWeaver, Web Dispatcher and HANA XS (CVE-2026-76964, CVE-2026-89126)
APPLE-SA-11-13-2026-1 tvOS 27.2.1
Home Assistant: the password is not the key — token secrets in cleartext, two token classes never expire, password change revokes none (2026.11.0, live-proven)
InfiniteWP Client: the NOSSL signing key has 31 bits of secret — recovered live in 291.9 seconds
Open WebUI: the Windows installer mints the master key from the install second — CVE-2025-15603 was rejected; here is the measurement
APPLE-SA-11-12-2026-1 HomeView Software Version 27.2
APPLE-SA-11-09-2026-9 visionOS 27.2.1
APPLE-SA-11-09-2026-8 watchOS 26.6.1
APPLE-SA-11-09-2026-7 watchOS 27.2.1
APPLE-SA-11-09-2026-6 macOS Sequoia 15.8.3
APPLE-SA-11-09-2026-5 macOS Tahoe 26.7.3
Log in Register Forum FAQ Memberlist Search
IT Security and Insecurity Portal

www.waraxe.us Forum Index -> Sql injection -> Is this... ?
Post new topicReply to topic View previous topic :: View next topic
Is this... ?
PostPosted: Tue Jul 27, 2004 5:42 pm Reply with quote
rain
Regular user
Regular user
Joined: Jun 29, 2004
Posts: 12




Code:

$result=mysql_query("SELECT * FROM user WHERE id='$id'",$db);
$row=mysql_fetch_row($result);

titulo("$row[1]");
echo"<p>$row[2]</p>";


Is this vurnable to sql injection? I think it is???
View user's profile Send private message
PostPosted: Fri Aug 13, 2004 12:14 am Reply with quote
Imster
Beginner
Beginner
Joined: Aug 13, 2004
Posts: 3




Quote:
Code:

$result=mysql_query("SELECT * FROM user WHERE id='$id'",$db);
$row=mysql_fetch_row($result);

titulo("$row[1]");
echo"<p>$row[2]</p>";



Is this vurnable to sql injection? I think it is???


It depends on the variable $id, if you are using stripslashes() then your fairly safe (safer than not using it anyway).

Code:

$id = stripslashes($id);

$result=mysql_query("SELECT * FROM user WHERE id='$id'",$db);
$row=mysql_fetch_row($result);

titulo("$row[1]");
echo"<p>$row[2]</p>";


Or if your going to be passing all sorts of variables at different times on different pages...you could make a custom function and include it on all pages where you want to make a variable safe. For example:

Make the file safe_inc.php and put:
Code:

function MakeSafe($sfe)
{
$sfe = stripslashes($sfe);
// add any custom code to make vars safe
return $sfe;
}


Then in the page you want to make safe...add this to the beginning:

Code:

include_once('safe_inc.php');


And then when you want to make a var safe do:
Code:

MakeSafe($variable_name);



I know its a long post to a simple question but I just wanted to show the methods to make vars safe in PHP in case any of you were at all interested. If not then I just wasted a minute of your life..

(Ps hi people im new here)
View user's profile Send private message Visit poster's website
PostPosted: Sun Aug 15, 2004 9:30 pm Reply with quote
madman
Active user
Active user
Joined: May 24, 2004
Posts: 46




Just an addition. Use addslashes instead of stripslashes. Smile
This code can be used to sanitize single- or double-quote regardless of magic quotes in effect:
Code:
function quote_me($str) {
while (preg_match('/\[\'"]?/', $str)) $str = stripslashes($str);
return addslashes($str);
}

$id = "0' OR password<>'";

$id = quote_me($id);
$sql = "SELECT username FROM table WHERE id = '$id'";


Use the previous method (that was called "safe" stripslashes), this is what we got:
Code:
SELECT username FROM table WHERE id = '0' OR password<>''

It will produce a doom! Smile

Using addslashes, the SQL query string would be:
Code:
SELECT username FROM table WHERE id = '0\' OR password=\''

That's what should called S A F E.

_________________
ch88rs,
madman
View user's profile Send private message
PostPosted: Wed Aug 18, 2004 10:55 am Reply with quote
Imster
Beginner
Beginner
Joined: Aug 13, 2004
Posts: 3




heh thanks. Will change my habbit now Embarassed
View user's profile Send private message Visit poster's website
PostPosted: Wed Aug 18, 2004 7:42 pm Reply with quote
madman
Active user
Active user
Joined: May 24, 2004
Posts: 46




To be honest, I never rely on addslashes() function only. Smile

_________________
ch88rs,
madman
View user's profile Send private message
Is this... ?
www.waraxe.us Forum Index -> Sql injection
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
All times are GMT
Page 1 of 1

Post new topicReply to topic


Powered by phpBB © 2001-2008 phpBB Group



PCWizardHub - Helping you fix, build, and optimize your PC life
All logos and trademarks in this site are property of their respective owner. The comments and posts are property of their posters, all the rest (c) 2004-2024 Janek Vind "waraxe"
Page Generation: 0.042 Seconds