STE WILLIAMS

Oz employment site suffers script kiddie attack

A group with the Twitter handle @BlackHatGhosts says it is behind breaking into the systems of Australian educational sector employment site Unijobs, posting the usernames and passwords of around 600 users on Pastebin.

First reported at The Conversation, the break-in follows the now-boring pattern of picking a small, softish target of no particular ideological value, punishing its users by publishing their details, and swaggering at the blow struck against heaven-knows-what imaginary enemy.

The site is operated by an Australian organization, the CBT Corp Unit Trust, a busy organization in operating small Web operations. Some are similar to Unijobs – Jobs4nurses.com.au, Govjobs.com.au, Tafejobs.com.au, WorldUniversityJobs.com, and Unijobs.co.nz – while others spread the organisation’s resources into other specalities such as the horse set (Equine.com.au), and a fledgling shopping app (I-shop.com.au).

Given the number of properties operated by the company, The Register contacted Unijobs to ascertain whether the attack would require upgrades or patches to any of its other properties. At the time of writing, no response has been received.

It should be noted that if Unijobs’ claims about its 40,000 user base are accurate, then the attack only affected a small number of its subscribers. reg

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2011/10/09/unijobs_hacked_by_jerks/

Homeland Security bungles ‘pre-crime’ tech test docs

The US Department of Homeland Security (DHS) has been testing its behavioral monitoring CCTV system on the public without the proper paperwork.

The Future Attribute Screening Technology (FAST) system uses high-resolution cameras and other “non-invasive” sensors to monitor human behavior, including “cardiovascular signals, pheromones, electrodermal activity, and respiratory measurements,” according to a 2008 DHS report on the project. This data is then fed into a computer system running matching algorithms that suggests which people should have their collars felt by local security.

The principle behind the whole system is that people with malicious intent will exhibit certain behaviors and biological responses that can be identified. The idea is to put these systems into US border-access points, and it’s a techniques which works very well in Israel – with the rather significant difference that the Israelis use people to do the analysis, rather than relying on software.

FAST has been under development for four years, under the auspices of the DHS Advanced Research Agency, and testing on the public was conducted this summer in the US Northeast. However, the DHS neglected to sort out the proper paperwork before using people as lab bunnies, according to documentation from a Freedom of Information request submitted by the Electronic Privacy Information Center (EPIC).

“Under the existing statutes, if they roll out a new technology like this there’s a need for a privacy-impact assessment,” Ginger McCall, open government counsel at EPIC, told The Register. “They didn’t do that.”

“It seems they would have a very high false positive rate, the best they say was that it’s 70 per cent effective,” McCall said. “When you consider the kinds of suspicions they raise it’s a lot of innocent people getting stopped.”

Well, a lot of innocent people might get stopped if the system were ever put into actual use. There are no “innocents” involved in current testing, however. A DHS source familiar with the testing told The Register that all the research was conducted on volunteers who were fully aware they were being watched. None of the data was stored after analysis, nor could it be tied to individual subjects.

In fact, the happy volunteers were even provided with tasty refreshments – no skulduggery here.

Our source said that the research – which monitors changes in thermal skin conductance, heart rate, respiration, pupil variation, and blink rate – is in the very early conceptual stages, and is in no way close to deployment.

The heavily-redacted testing report shows that around 200 people were put through the system on a two-day test run in Boston earlier this year. Judging from the photos in the report, the system isn’t ready for open deployment, but was instead used in a relatively enclosed space, suggesting a scanning unit similar to the millimeter wave detectors used today.

Hewing to the FAST facts as detailed in the 2008 report, deputy DHS press secretary Peter Boogaard told The Register in an email: “The Department’s Science and Technology Directorate has conducted preliminary research in operational settings to determine the feasibility of using non-invasive physiological and behavioral sensor technology and observational techniques to detect signs of stress, which are often associated with intent to do harm.

“The FAST program is only in the preliminary stages of research and there are no plans for acquiring or deploying this type of technology at this time.” ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2011/10/07/dhs_behavioral_scanning_on_public/

IE security hole sewn up for Patch Tuesday

IE security hole sewn up for Patch Tuesday

  • alert
  • print
  • comment
  • tweet

It’s that time of the month. Again

Free whitepaper – King’s College LondonUses IBM BNTRackSwitch for HPC

Microsoft is planning eight security updates next week – two critical – as part of its regular Patch Tuesday programme.

The obvious highlight of the batch is a critical update for Internet Explorer that affects all supported versions of Microsoft’s ubiquitous web browser, including IE 9. The second critical update covers flaws in Microsoft .NET Framework and Microsoft Silverlight that create a possible mechanism for miscreants to inject hostile code onto vulnerable systems.

The remaining six updates address lesser Windows vulnerabilities in Microsoft Forefront and Host Integration server. All six of these updates are rated as “important” and not all of them apply to all configurations. “IT administrators will have to evaluate to what degree they affect their networks, servers and workstation,” according to Wolfgang Kandek, CTO at security services firm Qualys.

As usual, more details on the flaws will emerge once Microsoft has published its patches on Tuesday. In the meantime all we have to go on is Redmond’s pre-release notice here. ®

Free whitepaper – Centre Hospitalier d’Avignon Secures Patient Records

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2011/10/07/ms_patch_tuesday_oct_pre_release/

AmEx ‘debug mode left site wide open’, says hacker

An alleged vulnerability on American Express site exposed customers to a serious security risk before the credit card giant closed down a portion of its site on Thursday afternoon.

Researcher Niklas Femerstrand claimed the problem arose because the debug mode of the americanexpress.com site had inexplicably been left on, thus providing access to vulnerable debug tools. The security shortcoming creating a possible mechanism to harvest users’ authentication cookies, according to Femerstrand.

American Express said the issue was confined to a test page it took down on Thursday afternoon. In a statement, issued to Financial News Network, it stressed that customer information was never at risk.

We learned this morning that an internal test page created to update promotional offers was temporarily accessible on our US website. The page did not contain CM information such as card number, name or address. The page in question has been taken down. We are not aware of any information at this time that this vulnerability was used for malicious purposes but we are continuing to investigate.

Femerstrand went public with his findings on Wednesday – posting what appears to be a harmless proof-of-concept illustration of the bug – after he struggled to report the bug directly to the credit card giant.

“The debugging tool is vulnerable to XSS [cross-site scripting] and it quickly becomes an issue when the debugging tools are called through unprotected GET parameters,” he said.

“The debug window refreshes itself so that injected code that doesn’t break the loop will execute infinitely. An attacker could inject a cookie stealer combined with jQuery’s .hide() and harvest cookies – which can, ironically enough, be exploited by using the admin panel provided by sloppy American Express developers.”

Femerstrand told El Reg on Thursday that the security vulnerability was still present hours after he went public about the flaw.

“The admin page is supposedly limited but debugging is still on and the vuln is still active,” he claimed via Twitter.

Reg reader David, who brought the issue to our attention, said any fix ought to have been easy to apply. “This should be simple to fix, but the potential for cookie harvesting and further exploration/exploitation is still there,” he said.

We asked American Express directly for comment on this story, which we’ll update as and when we hear more. ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2011/10/07/amex_website_security_snafu/

AmEx ‘debug mode left site wide open’, says hacker

An alleged vulnerability on American Express site exposed customers to a serious security risk before the credit card giant closed down a portion of its site on Thursday afternoon.

Researcher Niklas Femerstrand claimed the problem arose because the debug mode of the americanexpress.com site had inexplicably been left on, thus providing access to vulnerable debug tools. The security shortcoming creating a possible mechanism to harvest users’ authentication cookies, according to Femerstrand.

American Express said the issue was confined to a test page it took down on Thursday afternoon. In a statement, issued to Financial News Network, it stressed that customer information was never at risk.

We learned this morning that an internal test page created to update promotional offers was temporarily accessible on our US website. The page did not contain CM information such as card number, name or address. The page in question has been taken down. We are not aware of any information at this time that this vulnerability was used for malicious purposes but we are continuing to investigate.

Femerstrand went public with his findings on Wednesday – posting what appears to be a harmless proof-of-concept illustration of the bug – after he struggled to report the bug directly to the credit card giant.

“The debugging tool is vulnerable to XSS [cross-site scripting] and it quickly becomes an issue when the debugging tools are called through unprotected GET parameters,” he said.

“The debug window refreshes itself so that injected code that doesn’t break the loop will execute infinitely. An attacker could inject a cookie stealer combined with jQuery’s .hide() and harvest cookies – which can, ironically enough, be exploited by using the admin panel provided by sloppy American Express developers.”

Femerstrand told El Reg on Thursday that the security vulnerability was still present hours after he went public about the flaw.

“The admin page is supposedly limited but debugging is still on and the vuln is still active,” he claimed via Twitter.

Reg reader David, who brought the issue to our attention, said any fix ought to have been easy to apply. “This should be simple to fix, but the potential for cookie harvesting and further exploration/exploitation is still there,” he said.

We asked American Express directly for comment on this story, which we’ll update as and when we hear more. ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2011/10/07/amex_website_security_snafu/

AmEx ‘debug mode left site wide open’, says hacker

An alleged vulnerability on American Express site exposed customers to a serious security risk before the credit card giant closed down a portion of its site on Thursday afternoon.

Researcher Niklas Femerstrand claimed the problem arose because the debug mode of the americanexpress.com site had inexplicably been left on, thus providing access to vulnerable debug tools. The security shortcoming creating a possible mechanism to harvest users’ authentication cookies, according to Femerstrand.

American Express said the issue was confined to a test page it took down on Thursday afternoon. In a statement, issued to Financial News Network, it stressed that customer information was never at risk.

We learned this morning that an internal test page created to update promotional offers was temporarily accessible on our US website. The page did not contain CM information such as card number, name or address. The page in question has been taken down. We are not aware of any information at this time that this vulnerability was used for malicious purposes but we are continuing to investigate.

Femerstrand went public with his findings on Wednesday – posting what appears to be a harmless proof-of-concept illustration of the bug – after he struggled to report the bug directly to the credit card giant.

“The debugging tool is vulnerable to XSS [cross-site scripting] and it quickly becomes an issue when the debugging tools are called through unprotected GET parameters,” he said.

“The debug window refreshes itself so that injected code that doesn’t break the loop will execute infinitely. An attacker could inject a cookie stealer combined with jQuery’s .hide() and harvest cookies – which can, ironically enough, be exploited by using the admin panel provided by sloppy American Express developers.”

Femerstrand told El Reg on Thursday that the security vulnerability was still present hours after he went public about the flaw.

“The admin page is supposedly limited but debugging is still on and the vuln is still active,” he claimed via Twitter.

Reg reader David, who brought the issue to our attention, said any fix ought to have been easy to apply. “This should be simple to fix, but the potential for cookie harvesting and further exploration/exploitation is still there,” he said.

We asked American Express directly for comment on this story, which we’ll update as and when we hear more. ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2011/10/07/amex_website_security_snafu/

AmEx ‘debug mode left site wide open’, says hacker

An alleged vulnerability on American Express site exposed customers to a serious security risk before the credit card giant closed down a portion of its site on Thursday afternoon.

Researcher Niklas Femerstrand claimed the problem arose because the debug mode of the americanexpress.com site had inexplicably been left on, thus providing access to vulnerable debug tools. The security shortcoming creating a possible mechanism to harvest users’ authentication cookies, according to Femerstrand.

American Express said the issue was confined to a test page it took down on Thursday afternoon. In a statement, issued to Financial News Network, it stressed that customer information was never at risk.

We learned this morning that an internal test page created to update promotional offers was temporarily accessible on our US website. The page did not contain CM information such as card number, name or address. The page in question has been taken down. We are not aware of any information at this time that this vulnerability was used for malicious purposes but we are continuing to investigate.

Femerstrand went public with his findings on Wednesday – posting what appears to be a harmless proof-of-concept illustration of the bug – after he struggled to report the bug directly to the credit card giant.

“The debugging tool is vulnerable to XSS [cross-site scripting] and it quickly becomes an issue when the debugging tools are called through unprotected GET parameters,” he said.

“The debug window refreshes itself so that injected code that doesn’t break the loop will execute infinitely. An attacker could inject a cookie stealer combined with jQuery’s .hide() and harvest cookies – which can, ironically enough, be exploited by using the admin panel provided by sloppy American Express developers.”

Femerstrand told El Reg on Thursday that the security vulnerability was still present hours after he went public about the flaw.

“The admin page is supposedly limited but debugging is still on and the vuln is still active,” he claimed via Twitter.

Reg reader David, who brought the issue to our attention, said any fix ought to have been easy to apply. “This should be simple to fix, but the potential for cookie harvesting and further exploration/exploitation is still there,” he said.

We asked American Express directly for comment on this story, which we’ll update as and when we hear more. ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2011/10/07/amex_website_security_snafu/

AmEx ‘debug mode left site wide open’, says hacker

An alleged vulnerability on American Express site exposed customers to a serious security risk before the credit card giant closed down a portion of its site on Thursday afternoon.

Researcher Niklas Femerstrand claimed the problem arose because the debug mode of the americanexpress.com site had inexplicably been left on, thus providing access to vulnerable debug tools. The security shortcoming creating a possible mechanism to harvest users’ authentication cookies, according to Femerstrand.

American Express said the issue was confined to a test page it took down on Thursday afternoon. In a statement, issued to Financial News Network, it stressed that customer information was never at risk.

We learned this morning that an internal test page created to update promotional offers was temporarily accessible on our US website. The page did not contain CM information such as card number, name or address. The page in question has been taken down. We are not aware of any information at this time that this vulnerability was used for malicious purposes but we are continuing to investigate.

Femerstrand went public with his findings on Wednesday – posting what appears to be a harmless proof-of-concept illustration of the bug – after he struggled to report the bug directly to the credit card giant.

“The debugging tool is vulnerable to XSS [cross-site scripting] and it quickly becomes an issue when the debugging tools are called through unprotected GET parameters,” he said.

“The debug window refreshes itself so that injected code that doesn’t break the loop will execute infinitely. An attacker could inject a cookie stealer combined with jQuery’s .hide() and harvest cookies – which can, ironically enough, be exploited by using the admin panel provided by sloppy American Express developers.”

Femerstrand told El Reg on Thursday that the security vulnerability was still present hours after he went public about the flaw.

“The admin page is supposedly limited but debugging is still on and the vuln is still active,” he claimed via Twitter.

Reg reader David, who brought the issue to our attention, said any fix ought to have been easy to apply. “This should be simple to fix, but the potential for cookie harvesting and further exploration/exploitation is still there,” he said.

We asked American Express directly for comment on this story, which we’ll update as and when we hear more. ®

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2011/10/07/amex_website_security_snafu/

IE security hole sewn up for Patch Tuesday

IE security hole sewn up for Patch Tuesday

  • alert
  • print
  • comment
  • tweet

It’s that time of the month. Again

Free whitepaper – King’s College LondonUses IBM BNTRackSwitch for HPC

Microsoft is planning eight security updates next week – two critical – as part of its regular Patch Tuesday programme.

The obvious highlight of the batch is a critical update for Internet Explorer that affects all supported versions of Microsoft’s ubiquitous web browser, including IE 9. The second critical update covers flaws in Microsoft .NET Framework and Microsoft Silverlight that create a possible mechanism for miscreants to inject hostile code onto vulnerable systems.

The remaining six updates address lesser Windows vulnerabilities in Microsoft Forefront and Host Integration server. All six of these updates are rated as “important” and not all of them apply to all configurations. “IT administrators will have to evaluate to what degree they affect their networks, servers and workstation,” according to Wolfgang Kandek, CTO at security services firm Qualys.

As usual, more details on the flaws will emerge once Microsoft has published its patches on Tuesday. In the meantime all we have to go on is Redmond’s pre-release notice here. ®

Free whitepaper – Centre Hospitalier d’Avignon Secures Patient Records

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2011/10/07/ms_patch_tuesday_oct_pre_release/

IE security hole sewn up for Patch Tuesday

IE security hole sewn up for Patch Tuesday

  • alert
  • print
  • comment
  • tweet

It’s that time of the month. Again

Free whitepaper – King’s College LondonUses IBM BNTRackSwitch for HPC

Microsoft is planning eight security updates next week – two critical – as part of its regular Patch Tuesday programme.

The obvious highlight of the batch is a critical update for Internet Explorer that affects all supported versions of Microsoft’s ubiquitous web browser, including IE 9. The second critical update covers flaws in Microsoft .NET Framework and Microsoft Silverlight that create a possible mechanism for miscreants to inject hostile code onto vulnerable systems.

The remaining six updates address lesser Windows vulnerabilities in Microsoft Forefront and Host Integration server. All six of these updates are rated as “important” and not all of them apply to all configurations. “IT administrators will have to evaluate to what degree they affect their networks, servers and workstation,” according to Wolfgang Kandek, CTO at security services firm Qualys.

As usual, more details on the flaws will emerge once Microsoft has published its patches on Tuesday. In the meantime all we have to go on is Redmond’s pre-release notice here. ®

Free whitepaper – Centre Hospitalier d’Avignon Secures Patient Records

Article source: http://go.theregister.com/feed/www.theregister.co.uk/2011/10/07/ms_patch_tuesday_oct_pre_release/