Japan Airport Terminal Co Ltd is a company based out of Japan.
Consumers love 1% Realty because of the huge commission savings with professional service. This gives you a big advantage over the competition. As a new agent in the business, or a seasoned agent looking to do more business, with the 1% deal & national brand, you can compete against top agents for a listing and actually get it. Moreover, the more you do in that area, the more business will come. Having listings gets you more listings and clientele. The concept behind One Percent Realty is that we provide you full service but at a discount commission. The 1% system is designed so you don't have to go looking for business, once people know how much commission you are charging they jump at the chance to list their homes for sale and listings bring buyers. Not only is your office overhead really low with our no desk fees for working agents, but you also don't have to spend a fortune in marketing yourself to get the phone to ring. Both of these add to your bottom line and place more money in your pocket. Learn more at www.onepercentrealty.com
Security & Compliance Standards Overview
No incidents recorded for Japan Airport Terminal Co Ltd in 2025.
No incidents recorded for One Percent Realty Ltd., brokerage in 2025.
Japan Airport Terminal Co Ltd cyber incidents detection timeline including parent company and subsidiaries
One Percent Realty Ltd., brokerage cyber incidents detection timeline including parent company and subsidiaries
Last 3 Security & Risk Events by Company
FreePBX Endpoint Manager is a module for managing telephony endpoints in FreePBX systems. Versions prior to 16.0.96 and 17.0.1 through 17.0.9 have a weak default password. By default, this is a 6 digit numeric value which can be brute forced. (This is the app_password parameter). Depending on local configuration, this password could be the extension, voicemail, user manager, DPMA or EPM phone admin password. This issue is fixed in versions 16.0.96 and 17.0.10.
Neuron is a PHP framework for creating and orchestrating AI Agents. In versions 2.8.11 and below, the MySQLWriteTool executes arbitrary SQL provided by the caller using PDO::prepare() + execute() without semantic restrictions. This is consistent with the name (“write tool”), but in an LLM/agent context it becomes a high-risk capability: prompt injection or indirect prompt manipulation can cause execution of destructive queries such as DROP TABLE, TRUNCATE, DELETE, ALTER, or privilege-related statements (subject to DB permissions). Deployments that expose an agent with MySQLWriteTool enabled to untrusted input and/or run the tool with a DB user that has broad privileges are impacted. This issue is fixed in version 2.8.12.
Neuron is a PHP framework for creating and orchestrating AI Agents. Versions 2.8.11 and below use MySQLSelectTool, which is vulnerable to Read-Only Bypass. MySQLSelectTool is intended to be a read-only SQL tool (e.g., for LLM agent querying, however, validation based on the first keyword (e.g., SELECT) and a forbidden-keyword list does not block file-writing constructs such as INTO OUTFILE / INTO DUMPFILE. As a result, an attacker who can influence the tool input (e.g., via prompt injection through a public agent endpoint) may write arbitrary files to the DB server if the MySQL/MariaDB account has the FILE privilege and server configuration permits writes to a useful location (e.g., a web-accessible directory). This issue is fixed in version 2.8.12.
Okta Java Management SDK facilitates interactions with the Okta management API. In versions 11.0.0 through 20.0.0, race conditions may arise from concurrent requests using the ApiClient class. This could cause a status code or response header from one request’s response to influence another request’s response. This issue is fixed in version 20.0.1.
The Auth0 Next.js SDK is a library for implementing user authentication in Next.js applications. When using versions 4.11.0 through 4.11.2 and 4.12.0, simultaneous requests on the same client may result in improper lookups in the TokenRequestCache for the request results. This issue is fixed in versions 4.11.2 and 4.12.1.
