JustSystems Ichitaro Multiple Remote Code Execution Vulnerabilities



Date Discovered

November 4, 2010


Ichitaro is prone to multiple remote code-execution vulnerabilities. Attackers may exploit these issues to execute arbitrary code within the context of the vulnerable application. Failed attempts will result in a denial-of-service condition. Ichitaro versions 2004 through 2010 are vulnerable.

Technologies Affected

  • JustSystems Ichitaro 2004
  • JustSystems Ichitaro 2005
  • JustSystems Ichitaro 2006
  • JustSystems Ichitaro 2006 Government
  • JustSystems Ichitaro 2007
  • JustSystems Ichitaro 2007 Government
  • JustSystems Ichitaro 2008
  • JustSystems Ichitaro 2008 Government
  • JustSystems Ichitaro 2009
  • JustSystems Ichitaro 2009 Government
  • JustSystems Ichitaro 2010


Run all software as a nonprivileged user with minimal access rights.
To limit the impact of latent vulnerabilities, run the vulnerable application as an unprivileged user with minimal access rights.

Deploy network intrusion detection systems to monitor network traffic for malicious activity.
Deploy NIDS to monitor network traffic for signs of anomalous or suspicious activity such as unexplained incoming and outgoing traffic. This may indicate exploit attempts or activity that results from successful exploits.

Do not accept or execute files from untrusted or unknown sources.
Do not accept or open documents from unknown or untrusted individuals.

Implement multiple redundant layers of security.
Various memory-protection schemes (such as nonexecutable and randomly mapped memory segments) may hinder an attacker's ability to exploit this vulnerability to execute arbitrary code.

The vendor has released an advisory and updates. Please see the references for more information.




© 1995- Symantec Corporation

Permission to redistribute this alert electronically is granted as long as it is not edited in any way unless authorized by Symantec Security Response. Reprinting the whole or part of this alert in any medium other than electronically requires permission from secure@symantec.com.


The information in the advisory is believed to be accurate at the time of publishing based on currently available information. Use of the information constitutes acceptance for use in an AS IS condition. There are no warranties with regard to this information. Neither the author nor the publisher accepts any liability for any direct, indirect, or consequential loss or damage arising from use of, or reliance on, this information.

Symantec, Symantec products, Symantec Security Response, and secure@symantec.com are registered trademarks of Symantec Corp. and/or affiliated companies in the United States and other countries. All other registered and unregistered trademarks represented in this document are the sole property of their respective companies/owners.